All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jan Krüger" <jk@jk.gs>
To: git@vger.kernel.org
Subject: Re: [PATCH 2/2] builtin/symbolic-ref.c: add option to output shortened ref
Date: Mon, 27 Feb 2012 23:46:05 +0100	[thread overview]
Message-ID: <4F4C07AD.3050404@jk.gs> (raw)
In-Reply-To: <7vwr7752s8.fsf@alter.siamese.dyndns.org>

On 02/27/2012 11:28 PM, Junio C Hamano wrote:
> I think this one (unlike 1/2) makes sense, but a single letter -s feels a
> bit too vague.  Always spelling in long option "--short" so that it
> matches "%(refname:short)" in for-each-ref might be better, I would think.
> 
> Especially given that the expected use case is primarily in scripts not
> from the command line, being more explicit and easier to read has value
> over being short and easier to (mis)type.

Good point. If we can agree on what to do with the first patch, I'll
change that in the next iteration.

-Jan

  reply	other threads:[~2012-02-27 22:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-27 22:10 [PATCH 2/2] builtin/symbolic-ref.c: add option to output shortened ref Jan Krüger
2012-02-27 22:28 ` Junio C Hamano
2012-02-27 22:46   ` Jan Krüger [this message]
2012-02-27 23:04     ` Junio C Hamano
2012-02-27 23:54       ` 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=4F4C07AD.3050404@jk.gs \
    --to=jk@jk.gs \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.