#12555: Reimplement elements of Zp and Qp using templates
-------------------------------------+-------------------------------------
Reporter: roed | Owner: roed
Type: enhancement | Status: positive_review
Priority: major | Milestone: sage-6.1
Component: padics | Resolution:
Keywords: sd53 padics | Merged in:
templates | Reviewers: William Stein,
Authors: David Roe, Julian | Soroosh Yazdani, Julian Rueth,
Rueth | Travis Scrimshaw
Report Upstream: N/A | Work issues:
Branch: | Commit:
public/padics/templates-12555 | 0e7c96482eb0d2ee036906c79ecbc122f3650eda
Dependencies: #12625, #13299, | Stopgaps:
#14287, #12575, #6223 |
-------------------------------------+-------------------------------------
Comment (by jdemeyer):
Replying to [comment:64 jpflori]:
> Note sure from which trac ticket this is
#15185
> <hint hint> put trac ticket number into git commit messages...
If you have to ask people, that's not going to work. When I started as
release manager, I asked that and people forgot, were lazy, put the wrong
number... or worse: got angry because I was complaining over such trivial
things like ticket numbers in commit messages.
I learned that the only feasible solution is to have a system which
automatically added the ticket number to the commit message. With git that
cannot be done (that would be rewriting history), but at least automating
the mapping commit -> ticket number could be done some other way.
--
Ticket URL: <http://trac.sagemath.org/ticket/12555#comment:65>
Sage <http://www.sagemath.org>
Sage: Creating a Viable Open Source Alternative to Magma, Maple, Mathematica,
and MATLAB
--
You received this message because you are subscribed to the Google Groups
"sage-trac" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/sage-trac.
For more options, visit https://groups.google.com/groups/opt_out.
