#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: |
-------------------------------+--------------------------------------------
Changes (by leif):
* cc: kcrisman, leif (added)
Comment:
I think the description of commit messages is still somewhat misleading,
especially the first time they are mentioned.
IMHO one should almost always give a "long[er]" commit message, but in any
case the first line has to be one summarizing the whole patch.
(The example of Jeroen's long commit message might still confuse people,
since it consists of a few lines all starting with a ticket number, all
being "short" commit messages, i.e. summaries by themselves. For spkgs, I
usually copy the whole changelog entry from SPKG.txt into the [final]
commit message, below the summary and a blank line. Other commit messages
look similar.)
Karl-Dieter, you can perhaps better comment on the changes regarding
Mercurial's use of an editor to provide commit messages.
(To me, e.g. using Mercurial from the Sage prompt is more complicated than
using it directly from the shell. One does not have to record changeset
numbers, filename (and option) completion is available, not to mention
help etc. ...)
--
Ticket URL: <http://trac.sagemath.org/sage_trac/ticket/10190#comment:3>
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.
