From: Jerome Lovy <t2a2e9z8ncbs9qg@brefemail.com>
To: git@vger.kernel.org
Subject: Re: [RFC] A unique way to express "all" (vs "add vs "update") ?
Date: Mon, 18 Dec 2006 15:04:06 +0100 [thread overview]
Message-ID: <45869FD6.3030104@brefemail.com> (raw)
In-Reply-To: <87mz5o4v2v.wl%cworth@cworth.org>
Carl Worth wrote:
> On Fri, 15 Dec 2006 12:38:51 +0100, Jerome Lovy wrote:
>> While I am very happy with the refactorings undertaken with regard to
>> "git add/git commit" (both for UI and documentation), I am still a
>> little confused by the different ways I seem to find to express the idea
>> "I want to add (sort of) all file contents".
>
> I agree that there have been huge improvements---particularly in
> documentation. So thanks to everybody!
>
> Here's a simpler idea that might add the unification you're looking
> for. How about a new option:
>
> git add -a|--all
>
> This would allow "git commit -a|--all" to be understood as a simple
> helper for:
>
> git add -a|--all
> git commit
>
> That kind of unification seems like it could be helpful while learning
> things.
Exactly. I like it.
Now, it underlines the fact that this "--all" should IMHO rather be
called "--all-known" or the like - both for "add" and "commit" - but all
the same, I would be very happy with a more complete "git add" following
your proposed unification.
Jérôme
prev parent reply other threads:[~2006-12-18 14:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-15 11:38 [RFC] A unique way to express "all" (vs "add vs "update") ? Jerome Lovy
2006-12-15 12:09 ` Andreas Ericsson
2006-12-15 21:55 ` Junio C Hamano
2006-12-18 11:48 ` Jerome Lovy
2006-12-15 23:07 ` Carl Worth
2006-12-18 14:04 ` Jerome Lovy [this message]
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=45869FD6.3030104@brefemail.com \
--to=t2a2e9z8ncbs9qg@brefemail.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 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.