git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [RFC/PATCH] branch: show me the hot branches

From
Phil Hord <phil.hord@gmail.com>
Date
May 15, 2013, 12:54 UTC
Message-ID
<CABURp0oH-n59hbUzUefztf6DjJWR26Tu6zUX6VNQ292icwxh4w@mail.gmail.com>
In-Reply-To
<7vip2ldtlg.fsf@alter.siamese.dyndns.org>
On Tue, May 14, 2013 at 7:34 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 10 quoted lines
> Phil Hord <phil.hord@gmail.com> writes:
>
>> I imagine it with --date-order and whatnot.
>
> Perhaps modeled after this one.
>
>     git for-each-ref \
>         --format='%(refname:short) %(subject)'
>         --sort='-committerdate' refs/heads/
>

Nice. I had no idea about for-each-ref. I knew it was out there, but not what it could do. Another tool in the swiss army knife that is git.

I think Duy was right about his patch's merits.
Phil
Previous: Junio C HamanoNext: Duy Nguyen
Message 4 of 6 in “branch: show me the hot branches”
  1. branch: show me the hot branchesRamkumar Ramachandra, May 13, 2013
  2. Phil HordMay 14, 2013
  3. Junio C HamanoMay 14, 2013
  4. Phil HordMay 15, 2013
  5. Duy NguyenMay 15, 2013
  6. Ramkumar RamachandraMay 16, 2013

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.