From: Michael J Gruber <git@drmicha.warpmail.net>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Felipe Contreras <felipe.contreras@gmail.com>,
Git Mailing List <git@vger.kernel.org>,
Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] branch: add show-tracking option
Date: Thu, 16 May 2013 10:40:37 +0200 [thread overview]
Message-ID: <51949B85.40600@drmicha.warpmail.net> (raw)
In-Reply-To: <CACsJy8CrGTa2XdfFkkKDQQjF8gM3011RiUE6roe9L7yZZq5J2g@mail.gmail.com>
Duy Nguyen venit, vidit, dixit 16.05.2013 10:23:
> On Thu, May 16, 2013 at 3:00 PM, Michael J Gruber
> <git@drmicha.warpmail.net> wrote:
>> I feel, though, that we're really exploding our option and config realm.
>> For "git branch" in list mode, we are already able to stack "-v", i.e.
>> "-v" and "-vv" do different things. How about maybe adding "-vvv" and
>> arranging things so that the verbosity and the run time increases with
>> the number of v's?
>>
>> -v list with sha1 + subject of last commit
>> -vv add upstream branch name
>> -vvv add ahead/behind info (the only costly mode)
>> -vvvv same with "--cherry" (ahead/behind/same)
>>
>> Or maybe combine the middle two cases into "-vv", which means it would
>> be the same as "-vv", with only "-v" changing what it does now.
>
> What if I want something in -vvvv except some in -vv? I think to avoid
> option explosion, maybe we can adopt --pretty=format:xxx from "git
> log" and let the user decideswhat (and how) to display. "pretty" code
> learns about alignment already, which may be useful here.
> --
> Duy
Sure, that is the big solution we've been talking about. Unify
for-each-ref formats and log formats and use that. After all, "git
branch" in list mode really is for-each-ref, and should be transparently
so; same goes for "git tag". Think "git rev-list" and "git ref-list"!
But I guess we'll be compabeaten ;)
Michael
next prev parent reply other threads:[~2013-05-16 8:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 7:48 [PATCH] branch: add show-tracking option Felipe Contreras
2013-05-16 7:51 ` Felipe Contreras
2013-05-16 7:54 ` Duy Nguyen
2013-05-16 7:57 ` Felipe Contreras
2013-05-16 8:00 ` Michael J Gruber
2013-05-16 8:09 ` Felipe Contreras
2013-05-16 8:23 ` Michael J Gruber
2013-05-16 8:23 ` Duy Nguyen
2013-05-16 8:40 ` Michael J Gruber [this message]
2013-05-16 8:56 ` Duy Nguyen
2013-05-16 16:17 ` Junio C Hamano
2013-05-16 16:28 ` Felipe Contreras
2013-05-16 16:31 ` Junio C Hamano
2013-05-16 16:33 ` 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=51949B85.40600@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=felipe.contreras@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pclouds@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).