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

[Nguyen Thai Ngoc Duy]

On Thu, May 3, 2012 at 7:33 AM, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
> Steven Rostedt <rostedt@xxxxxxxxxxx> 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...

There's also a patch that adds sorting support to "git branch":

http://thread.gmane.org/gmane.comp.version-control.git/188705
-- 
Duy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/