Messages in this thread | | | Subject | Re: [PATCH 0/2] [GIT PULL] ktest: A couple of fixes | From | Steven Rostedt <> | Date | Wed, 02 May 2012 21:52:24 -0400 |
| |
On Wed, 2012-05-02 at 17:33 -0700, Jakub Narebski wrote: > Steven Rostedt <rostedt@goodmis.org> writes:
> Well, there is "git branch -v -v": > > $ git branch -v -v > [...] > gsoc2012-wiki 0e71ecb [gsoc2012/wiki/master: ahead 11, behind 4] '"Published" and "secret" commits' project > html 8b94cd8 Autogenerated HTML docs for v1.7.7.1-488-ge8e1c > i18n-po.pl aa8ce2e [git-i18n/ab/i18n-po: ahead 1] po/pl.po: Eliminate fuzzy translations > maint bf50515 Git 1.7.10.1 > [...] > t/doc-config-extraction 451c2ef [git/trast/t/doc-config-extraction-v2: ahead 2257, behind 3] Documentation: complete config list from other manpages > test b77178e gitweb: Separate features with no project specific override > todo 10c7888 Meta/dodoc: assign default values > user-manual 4c22f3d Comments to user-manual (WIP) > > > I guess that git-for-each-ref could be extended with behind / ahead > information, perhaps as modifiers to existing %(upstream) field...
Would that list them in order then? Also, having the date printed is useful, as I sometimes remember the approximate date a I worked on something.
> > P.S. I would associate "git ls" with listing worktree files. >
Yeah, I agree. I just wanted a script that had a short and easy name ;-)
git branch-sort
would probably be a better name.
| |