Francois Bissey wrote:
Comments, especially about patches are still welcome. But a lot of stuff should
just go in the commit message.
"The" commit message, hopefully.
In short, what is the git command to get a summary of the changes related
to a package, with pointers to the related trac tickets ?
I'll concede that it looks messy to me at the moment. With mercurial we had a
rather well enforced rule of putting the trac ticket number in each commit
message.
It is probably a good idea to continue that practice.
If you look at github you can get the commit history of a particular file. But
since the
change to git the ticket number is often absent (at least in the commits I was
interested in).
Changes (by vbraun):
...
Comment:
There is no need to mention the ticket number in the commit message
FYI.
Of course you can write anything, but in general there is no guarantee
that the ticket number in the commit ends up being the ticket
number that
merges said commit.
Sorry for hijacking,
-leif
--
() The ASCII Ribbon Campaign
/\ Help Cure HTML E-Mail
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@googlegroups.com.
Visit this group at http://groups.google.com/group/sage-devel.
For more options, visit https://groups.google.com/d/optout.
