git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Miles Bader <miles@gnu.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Nguyen Thai Ngoc Duy <pclouds@gmail.com>,
	git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: [PATCHv2 3/3] git-add: rename -u to -a
Date: Mon, 28 Feb 2011 10:08:53 +0100	[thread overview]
Message-ID: <4D6B6625.9080104@drmicha.warpmail.net> (raw)
In-Reply-To: <buobp1w350a.fsf@dhlpc061.dev.necel.com>

Miles Bader venit, vidit, dixit 28.02.2011 10:03:
> Michael J Gruber <git@drmicha.warpmail.net> writes:
>> Miles Bader venit, vidit, dixit 28.02.2011 09:42:
>>> Michael J Gruber <git@drmicha.warpmail.net> writes:
>>>> - "commit -a,--add <addopts>" be "add <addopts> && commit", and
>>>
>>> Can you give an example?  It look like you're proposing that the user
>>> would have to type "commit -a -u", which is pretty gross for a fairly
>>> common operation that already has a good shorthand...
>>
>> we don't need "-u" any more, because it's the new default. So,
>> obviously, "commit -a" would do what it always did.
> 
> Ok, so for "-u" that works out.
> 
> But for -A, the user would have to type "commit -a -A".
> 
> That sort of indirection is clever, but it seems confusing and
> inconvenient for the user, and I think a very common question would be
> "why do I need to use -a when it's obvious that -A should imply that?"

If it's obviously an add option, then it will imply add, of course. I'm
trying to make things better ;)

That whole last paragraph was labelled "radical brain-storming", not
incorporating other add-related commit options like -i and -o, not
completely thought through.

Michael

  reply	other threads:[~2011-02-28  9:12 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-25 14:45 [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-25 14:45 ` [PATCH/RFC 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-25 19:04   ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 2/3] git-commit: rename --all to --track Michael J Gruber
2011-02-25 19:08   ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-25 19:40   ` Junio C Hamano
     [not found] ` <7vr5aw9b7m.fsf@alter.siamese.dyndns.org>
2011-02-26 10:30   ` [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-27 15:50     ` [PATCHv2 " Michael J Gruber
2011-02-27 15:50       ` [PATCHv2 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-27 23:35         ` Junio C Hamano
2011-02-27 15:50       ` [PATCHv2 2/3] git-commit: rename --all to --all-tracked Michael J Gruber
2011-02-27 15:50       ` [PATCHv2 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-27 16:38         ` Nguyen Thai Ngoc Duy
2011-02-28  6:40           ` Junio C Hamano
2011-02-28  8:30             ` Michael J Gruber
2011-02-28  8:42               ` Miles Bader
2011-02-28  8:46                 ` Michael J Gruber
2011-02-28  8:53                   ` Miles Bader
2011-02-28  9:05                     ` Snipping on this list (Was: Re: [PATCHv2 3/3] git-add: rename -u to -a) Michael J Gruber
2011-02-28 18:18                       ` Snipping on this list Junio C Hamano
2011-02-28  9:03                   ` [PATCHv2 3/3] git-add: rename -u to -a Miles Bader
2011-02-28  9:08                     ` Michael J Gruber [this message]
2011-02-28  9:40               ` Matthieu Moy
2011-02-28  9:49                 ` Michael J Gruber
2011-02-28 10:01                   ` Tor Arntsen
2011-02-28 10:03                     ` Michael J Gruber
2011-02-28 10:05                   ` Matthieu Moy
2011-02-28 10:53                     ` Michael J Gruber
2011-02-28 18:21                 ` 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=4D6B6625.9080104@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=miles@gnu.org \
    --cc=pclouds@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).