From: "Nikolai Weibull" <now@bitwi.se>
To: "Junio C Hamano" <junkio@cox.net>
Cc: "Karl Hasselström" <kha@treskal.com>, git@vger.kernel.org
Subject: Re: [PATCH] git-add -u: match the index with working tree.
Date: Fri, 20 Apr 2007 13:18:25 +0200 [thread overview]
Message-ID: <dbfc82860704200418o4d27b5a6pc3ea2f5abe25be8e@mail.gmail.com> (raw)
In-Reply-To: <7virbrz47b.fsf@assigned-by-dhcp.cox.net>
On 4/20/07, Junio C Hamano <junkio@cox.net> wrote:
> Karl Hasselström <kha@treskal.com> writes:
>
> > On 2007-04-20 01:42:18 -0700, Junio C Hamano wrote:
> >
> >> This is a shorthand of what "git commit -a" does in preparation
> >> for making a commit,
> > [snip]
> >> -"git-add [-n] [-v] [-f] [--interactive | -i] [--] <filepattern>...";
> >> +"git-add [-n] [-v] [-f] [--interactive | -i] [-u] [--] <filepattern>...";
> >
> > Any particular reason for choosing a different letter than the
> > -a/--all that git commit uses?
>
> Haven't I explain that elsewhere already?
Yes, in <7vzm531ly3.fsf@assigned-by-dhcp.cox.net>.
Specifically:
> I picked "-u" instead of "-a" because I wanted to stress that
> this is about "updating" (which has connotation that it is
> relative to something, and in this case it is relative to the
> current "index"), and not about "all", which "-a" would imply.
nikolai
next prev parent reply other threads:[~2007-04-20 11:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-20 8:42 [PATCH] git-add -u: match the index with working tree Junio C Hamano
2007-04-20 8:42 ` [PATCH] Do not show progress meter while checking files out Junio C Hamano
2007-04-20 9:37 ` Johannes Sixt
2007-04-20 12:37 ` Andy Parkins
2007-04-20 12:46 ` Matthieu Moy
2007-04-20 13:04 ` Nicolas Pitre
2007-04-20 14:46 ` Shawn O. Pearce
2007-04-20 13:12 ` J. Bruce Fields
2007-04-20 10:49 ` [PATCH] git-add -u: match the index with working tree Karl Hasselström
2007-04-20 11:16 ` Junio C Hamano
2007-04-20 11:18 ` Nikolai Weibull [this message]
2007-04-20 11:39 ` Karl Hasselström
2007-04-20 11:17 ` 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=dbfc82860704200418o4d27b5a6pc3ea2f5abe25be8e@mail.gmail.com \
--to=now@bitwi.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=kha@treskal.com \
/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).