From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: <git@vger.kernel.org>
Subject: Re: [PATCH] git-add: allow --ignore-missing always, not just in dry run
Date: Thu, 19 Jan 2012 12:03:17 +0100 [thread overview]
Message-ID: <8762g87y4q.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <7vobu0liwj.fsf@alter.siamese.dyndns.org> (Junio C. Hamano's message of "Wed, 18 Jan 2012 14:56:12 -0800")
[dropped Dieter as this really goes off on an internal tangent]
Junio C Hamano <gitster@pobox.com> writes:
> If somebody is writing a script using "git add" (which is not recommended
> to begin with)
Can we still stick to that stance? Our tests are increasingly using
'git add' instead of 'git update-index --add':
$ git grep 'git[ -]add' t/ | wc -l
1540
$ git grep 'git[ -]update-index --add' t/ | wc -l
269
$ git grep 'git[ -]update-index --add' v1.6.0 t/ | wc -l
251
$ git grep 'git[ -]add' v1.6.0 t/ | wc -l
705
So while git(1) still says git-add is porcelain (and thus not to be used
for scripting), it has mostly superseded 'git update-index --add' in new
script usage even within git.git. I suspect the same goes for things
like git-rm, git-commit, etc.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-01-19 11:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-18 21:52 [PATCH] git-add: allow --ignore-missing always, not just in dry run Dieter Plaetinck
2012-01-18 22:56 ` Junio C Hamano
2012-01-19 10:52 ` Dieter Plaetinck
2012-01-19 21:26 ` Junio C Hamano
2012-01-20 18:14 ` Dieter Plaetinck
2012-01-19 11:03 ` Thomas Rast [this message]
2012-01-19 18:46 ` Junio C Hamano
2012-01-20 12:56 ` Thomas Rast
2012-01-20 18:03 ` Junio C Hamano
2012-02-07 4:39 ` Mike Gant
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=8762g87y4q.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).