A followup: I wanted to know which trac ticket was responsible for sagenb-0.11.0, so I did
git log build/pkgs/sagenb/package-version.txt The sha1 for the relevant change was c5354abd32c0f396ab06a46a4141e77ce487eb8e. So I did git describe --abbrev=0 c5354abd32c0f396ab06a46a4141e77ce487eb8e and was told "6.2.rc1", which is completely wrong: I know that the change was either in 6.4.rc0 or 6.4.rc1. So I did git log and searched for "c5354". I then found ticket #16911, but when I looked at the commits listed at #16911, it didn't seem to have this change. So now I'm really confused. Can anyone clarify what's going on? In particular: - why didn't "git describe --abbrev=0 ..." work? - how do I figure out which trac ticket caused a particular change? John On Tuesday, October 7, 2014 11:52:00 PM UTC-7, Nicolas M. Thiéry wrote: > > On Tue, Oct 07, 2014 at 04:30:23PM -0700, R. Andrew Ohana wrote: > > You can get the beta into which the release manager merged the ticket > > (i.e. the beta that you want minus 1) with > > git describe --abbrev=0 TICKET_SHA1 > > where TICKET_SHA1 is the sha1 of the merge commit for the ticket in > > question (i.e. the first sha1 in git trac log TICKET). > > Maybe a good candidate for a git trac command? > > > git trac status 13242 > new > > > git trac status 13243 > needs review > > > git trac status 17987 > merged in 6.4.beta 2 > > Thanks in advance! > > Cheers, > Nicolas > -- > Nicolas M. Thiéry "Isil" <[email protected] <javascript:>> > http://Nicolas.Thiery.name/ > -- You received this message because you are subscribed to the Google Groups "sage-git" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
