On Tue, 27 May 2014 17:59:17 John H Palmieri wrote: > On Tuesday, May 27, 2014 5:06:16 PM UTC-7, François wrote: > > On Wed, 14 May 2014 06:57:53 Volker Braun wrote: > > > On Wednesday, May 14, 2014 11:54:56 AM UTC+1, Thierry > > > > > > (sage-googlesucks@xxx) wrote: > > > > In short, what is the git command to get a summary of the changes > > > > related > > > > > > to a package > > > > > > git log build/pkgs/<package_name> > > > > > > git trac find <sha1> > > > > > > Various combinations could also be scripted but I don't really see the > > > need, ie., it doesn't feature in my workflow. If your workflow differs > > > > you > > > > > can easily build your own tools using these building blocks. > > > > How do you get "git trac find ...." to work? > > > > I am getting "'trac' is not a git command" > > I think that if you do "sage -i git_trac", it should install it for you. > (Or follow the directions from the link Leif posted.) > > John
Thanks for all the pointers. You and Leif have provided me useful info here. Francois -- 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.
