The "git trac log <ticket>" only inspects the log of the current branch (just like "git log", except that it understands trac ticket numbers). So you need to be on a sufficiently recent branch if you want the log of these tickets.
On Tuesday, September 9, 2014 5:56:28 PM UTC+1, Clemens Heuberger wrote: > > I get (git-trac-command at 7e8fb34) > > $ git trac log 16538 > Error: release manager has not merged Trac #16538 > $ git trac log 16943 > Error: release manager has not merged Trac #16943 > $ git trac log 16786 > Error: release manager has not merged Trac #16786 > > Actually, #16538 has been merged in 6.4.beta0, > #16943 is closed, but not in a published develop branch, > #16786 is "needs_review". > > The error message is given without the usual delay incurred when > contacting the > trac server: > > $ time git trac log 16943 > Error: release manager has not merged Trac #16943 > > real 0m0.112s > user 0m0.069s > sys 0m0.018s > > compared to > > $ time git trac print 16943 > ... > real 0m1.070s > user 0m0.057s > sys 0m0.014s > > All of the above: Linux Mint 13 Maya, 3.13.0-32-generic > #57~precise1-Ubuntu > -- 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.
