Re: [PATCH 0/2] [GIT PULL] ktest: A couple of fixes

[Jakub Narebski <jnareb@gmail.com>]

Steven Rostedt <rostedt@goodmis.org> writes:

> I'll throw in one more feature request, that you can take or leave (I
> have another script for it ;-), something that does a listing of
> branches in order of date. I have over a hundred branches in my repo,
> and I forget which branch was the last one I was working on. So I
> created a script called git-ls (attached).
> 
> Here's what the output looks like:
> 
> $ git-ls | tail
> 681d1c4    2012-04-19    trace/tip/perf/urgent                         tracing: Fix stacktrace of latency tracers (irqsoff and friends)
> 59cfede    2012-04-19    trace/rfc/iolatency                           tracing: Add iolatency tracer
> 61463fa    2012-04-24    trace/tip/perf/core                           ftrace/x86: Remove the complex ftrace NMI handling code
> e201738    2012-04-26    trace/tip/perf/core-2                         ftrace/x86: Remove the complex ftrace NMI handling code
> 053cef1    2012-04-27    trace/rfc/tracing/fentry                      ftrace/x86: Add support for -mfentry to x86_64
> 4a6d70c    2012-04-27    trace/tip/perf/core-3                         ftrace/x86: Remove the complex ftrace NMI handling code
> a76c3eb    2012-04-30    trace/rfc/kprobes/ftrace                      ftrace/x86: Add support for x86_32 to pass pt_regs to function tracer
> 6e1b77e    2012-05-02    trace/rfc/kprobes/ftrace-v2                   kprobes: Update header for ftrace optimization
> a4cc5f1    2012-05-02    trace/tip/perf/next-2                         ftrace/x86: Add separate function to save regs
> 9bd8569    2012-05-02    trace/tip/perf/next                           trace: Make removal of ring buffer pages atomic
> 
> It lists the branches in order of date of last commit.
> 
> Again, just showing some things that I find useful. If no one else finds
> these interesting, then just ignore it. I have my scripts :-)

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...

P.S. I would associate "git ls" with listing worktree files.

-- 
Jakub Narebski