From: Michael J Gruber <git@drmicha.warpmail.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: John Tapsell <johnflux@gmail.com>, Git List <git@vger.kernel.org>,
Jeff King <peff@peff.net>
Subject: Re: Improving git branch
Date: Thu, 18 Dec 2014 11:05:12 +0100 [thread overview]
Message-ID: <5492A6D8.8060509@drmicha.warpmail.net> (raw)
In-Reply-To: <xmqqvbla80bm.fsf@gitster.dls.corp.google.com>
Junio C Hamano schrieb am 17.12.2014 um 21:53:
> 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?
>
If "waiting for Peff to be bored" is not a bold strategy then I don't
know what would be one ;)
Seriously, I didn't feel bold enough to claim that this is agreed upon
but I am more than happy that it is!
If I can squeeze out some more git time from my other obligations I'll
try and help.
Michael
next prev parent reply other threads:[~2014-12-18 10:05 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
2014-12-17 21:01 ` Jeff King
2014-12-21 16:36 ` Moritz Neeb
2014-12-18 10:05 ` Michael J Gruber [this message]
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=5492A6D8.8060509@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).