git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Jeremy Apthorp <nornagon@nornagon.net>
Cc: git@vger.kernel.org
Subject: Re: Branch list by date
Date: Wed, 9 Jul 2014 01:21:14 -0400	[thread overview]
Message-ID: <20140709052114.GC2318@sigill.intra.peff.net> (raw)
In-Reply-To: <CAMxk9GhQs_kF5573MS1SJ6a7UZuPu+oquXidOOvibznLQ7_FWw@mail.gmail.com>

On Mon, Jul 07, 2014 at 09:54:55PM -0700, Jeremy Apthorp wrote:

> I write this missive with dual purpose: firstly to share a potentially
> useful tool, and secondly to suggest that this feature (with a less
> mind-wrenchingly disgusting implementation) might be included in
> mainline git, as for example `git branch [-t] | [--by-time]`.

I think what we should aim for is:

  1. Teaching git-branch the same sorting as for-each-ref. So first
     --sort, and then possibly "-t" as an alias for "--sort=committerdate".

  2. Teaching git-branch custom output formats. We have "-v" and "-vv",
     but it should support the full power of for-each-ref's --format
     atoms.

  3. Teach branch and for-each-ref to support readable colors in their
     formats, like we do for "log --format".

  4. Optionally add config options to configure defaults for the above,
     so "git branch" shows what you want.

I'm (slowly) working on a refactor that will unify for-each-ref and
branch, which would accomplish (1) and (2).

-Peff

      reply	other threads:[~2014-07-09  5:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-08  4:54 Branch list by date Jeremy Apthorp
2014-07-09  5:21 ` Jeff King [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20140709052114.GC2318@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=nornagon@nornagon.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).