From: Jeff King <peff@peff.net>
To: Samuel Maftoul <samuel.maftoul@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: [RFC] implement branch.sort config option
Date: Mon, 13 Aug 2018 13:46:43 -0400 [thread overview]
Message-ID: <20180813174643.GA8790@sigill.intra.peff.net> (raw)
In-Reply-To: <CAFj+z06S1V3Z7Z0zKPSrpZfWuzku9PTYjG+uu6ig-yCnG4FCLw@mail.gmail.com>
On Mon, Aug 13, 2018 at 11:56:58AM +0200, Samuel Maftoul wrote:
> Currently, you can:
>
> git tag --sort=$sorting_key
>
> You can also do this on branches:
>
> git branch --sort=$sorting_key
>
> For tags, you can also configure it with a config key:
>
> git config tag.sort $sorting_key
>
> But there is no corresponding config for sorting branches.
>
> Locally, I have a (pretty simple) patch that implements the
> branch.sort config key.
> Should I contribute that ?
Yes, that seems like a useful feature to me, and as you point out it
makes the overall interface more consistent.
-Peff
next prev parent reply other threads:[~2018-08-13 17:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-13 9:56 [RFC] implement branch.sort config option Samuel Maftoul
2018-08-13 17:46 ` Jeff King [this message]
2018-08-13 19:18 ` Junio C Hamano
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=20180813174643.GA8790@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=samuel.maftoul@gmail.com \
/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).