From: Junio C Hamano <gitster@pobox.com>
To: Michael J Gruber <git@drmicha.warpmail.net>
Cc: John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>,
Jeff King <peff@peff.net>
Subject: Re: Improving git branch
Date: Wed, 17 Dec 2014 12:53:49 -0800 [thread overview]
Message-ID: <xmqqvbla80bm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <549168DD.1080906@drmicha.warpmail.net> (Michael J. Gruber's message of "Wed, 17 Dec 2014 12:28:29 +0100")
Michael J Gruber <git@drmicha.warpmail.net> writes:
> Rather than extending "git branch" any further[*], I suggest a bolder
> strategy:
>
> - unify/merge for-each-ref and pretty formats (and code) as far as possible
> - leverage that for the list modes of branch and tag
>
> That would allow everyone to get their favourite listing, just like for
> logs. Otherwise it would be very difficult to agree on *the* proper
> format for an extended branch or tag list.
>
> Michael
>
>
> [*] I know I'm a sinner, too.
Actually this is not a "bolder" strategy, but the unification has
been discussed and agreed to be the longer-term direction for quite
a while, I think. Didn't Peff have this in his "things to do when
absolutely bored" box?
next prev parent reply other threads:[~2014-12-17 20:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-17 11:10 Improving git branch John Tapsell
2014-12-17 11:28 ` Michael J Gruber
2014-12-17 11:51 ` John Tapsell
2014-12-17 12:23 ` Michael J Gruber
2014-12-17 20:53 ` Junio C Hamano [this message]
2014-12-17 21:01 ` Jeff King
2014-12-21 16:36 ` Moritz Neeb
2014-12-18 10:05 ` Michael J Gruber
2014-12-17 20:51 ` 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=xmqqvbla80bm.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=johnflux@gmail.com \
--cc=peff@peff.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).