Hi,

I just did "hg log" and I'm concerned with the way ticket numbers
appear in log messages.  Here's the top few in sage-5.0.beta2:

summary:     Trac #12396: #12396: these whitespace changes are needed
for the new doctest framework
summary:     Trac #12390: trac 12390 -- the documentation for
number_of_partitions mentions a
summary:     Trac #10333: #10333: Optional interface to Anders Buch's
LR calculator
summary:     Trac #12094: Bump Maxima to 5.24.0.
summary:     Trac #10959: Trac 10959: add_edge automatically adds
newly created vertex to some partition
summary:     Trac #6804: Trac #6804: change '=' to '>=' in the
docstring for Permutation.weak_excedences()
summary:     Trac #12068: Reviewer patch fixing trivial formatting issue
summary:     Trac #12068: #12068: Numerator for symbolic expression should'nt us

Basically, all but one of them is redundant, in many different ways.
Even if the person making the patch puts -- what appears I guess -- to
be the canonical format, they still get another copy of that prepended
("Trac #6804: Trac #6804:").    This has been the case for almost
every commit message for well over a year.   What's going on here?

It's important (in fact, critical) that the trac ticket number is
clearly available in the commit message.  But having it twice in two
different ways in almost every message seems a little bit sloppy to
me.  The first "Trac #num" message is probably being added by some
script that Jereon wrote...  maybe that script needs to be a little
more sophisticated?

 - William


-- 
William Stein
Professor of Mathematics
University of Washington
http://wstein.org

-- 
To post to this group, send an email to sage-devel@googlegroups.com
To unsubscribe from this group, send an email to 
sage-devel+unsubscr...@googlegroups.com
For more options, visit this group at http://groups.google.com/group/sage-devel
URL: http://www.sagemath.org

Reply via email to