git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Subject: [RFC/PATCH 0/2] RFC/POC: patterns for branch list
Date: Wed, 27 Apr 2011 14:15:17 +0200	[thread overview]
Message-ID: <cover.1303906496.git.git@drmicha.warpmail.net> (raw)

This mini series is about introducing patterns to the list mode of
'git branch' much like the pattern for 'git tag -l'. There are several
things which I would like to do but would like to rfc first:

'-l' is the natural short option name for '--list'. This is taken for the
rarely used or needed 'create reflog' option. I'd change the latter to
'-g,--create-reflog' (cmp. log) and take '-l,--list' but know the reaction
already.

'-v' and '-vv' both take considerable time (because they need to walk).
It makes more sense to have '-v' display cheap output (upstream name)
and '-vv' add expensive output (ahead/behind info). '-vvv' could add super
expensive info (ahead/equivalent/behind a la cherry-mark).

But all of the above are changes to current (ui) behaviour. In the two patches
below, only the automatic activation of the list mode with -v/-vv is a
change of (undocumented) behaviour.

And yes, git-for-each-ref can do all this and more, but that is plumbing.

Michael J Gruber (2):
  branch: allow pattern arguments
  branch: introduce --list argument

 builtin/branch.c |   21 +++++++++++++++------
 1 files changed, 15 insertions(+), 6 deletions(-)

-- 
1.7.5.270.gafca7

             reply	other threads:[~2011-04-27 12:15 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27 12:15 Michael J Gruber [this message]
2011-04-27 12:15 ` [RFC/PATCH 1/2] branch: allow pattern arguments Michael J Gruber
2011-04-27 12:15 ` [RFC/PATCH 2/2] branch: introduce --list argument Michael J Gruber
2011-04-27 17:10 ` [RFC/PATCH 0/2] RFC/POC: patterns for branch list 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=cover.1303906496.git.git@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    /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).