git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Bradly Feeley <bradlyf@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Inconsistency with -a vs -A
Date: Mon, 18 Apr 2011 08:25:53 +0200	[thread overview]
Message-ID: <4DABD971.20108@drmicha.warpmail.net> (raw)
In-Reply-To: <loom.20110418T051443-551@post.gmane.org>

Bradly Feeley venit, vidit, dixit 18.04.2011 05:20:
> I was curious if there was a reason that some command use -a and some command
> use -A. For example, to view all branches the lowercase switch 'a' is used, but
> when staging all files with add an uppercase 'A'. Of course I always pick the
> wrong one when running either command. Is there a reason for the inconsistency?

Yes.

> Do you think they should be made the same?

Yes, I do :) For more details on both "yes", see:

http://permalink.gmane.org/gmane.comp.version-control.git/167907

Cheers,
Michael

  reply	other threads:[~2011-04-18  6:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-18  3:20 Inconsistency with -a vs -A Bradly Feeley
2011-04-18  6:25 ` Michael J Gruber [this message]
2011-04-18  9:56 ` Junio C Hamano
2011-04-18 15:04   ` 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=4DABD971.20108@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=bradlyf@gmail.com \
    --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).