#10190: developer's guide: new chapter "Advanced Mercurial Usage"
-------------------------------+--------------------------------------------
Reporter: mvngu | Owner: mvngu
Type: enhancement | Status: needs_review
Priority: major | Milestone: sage-4.6.1
Component: documentation | Keywords: Mercurial, developer's guide
Author: Minh Van Nguyen | Upstream: N/A
Reviewer: | Merged:
Work_issues: |
-------------------------------+--------------------------------------------
Comment(by rbeezer):
Replying to [comment:3 leif]:
> I think the description of commit messages is still somewhat misleading,
especially the first time they are mentioned.
I'm in the middle of reviewing this one. I wrote much of the walk-
through. At one time I was given the impression a one-line message was
best. Thus the strident "one-line" request.
I agree that a multi-line commit can be an improvement. Personally, I
would go back to Trac if I wanted to know more. So I don't necessarily
agree that they should be required or preferred. As a patch author, I've
always found one line sufficient (and less work!).
What I have seen is rookie developers put gobs of stuff in the commit
message, with no summary line. Not pretty. So a more thorough discussion
in the advanced section is a good compromise I think. What would you
suggest for the introductory discussion?
Re: editors,
{{{hg qrefresh -m "#xxxx: Summary..."}}}
is my optimal solution. But not good for multi-line stuff.
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10190#comment:4>
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 post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/sage-trac?hl=en.
