From: Junio C Hamano <gitster@pobox•com>
To: Matthew Cline <matt@nightrealms•com>
Cc: git@vger•kernel.org
Subject: Re: Feature request: Config option for --no-ignore-removal/--ignore-removal
Date: Wed, 16 Oct 2013 14:38:49 -0700 [thread overview]
Message-ID: <xmqqli1s6gly.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: 1380081691.7963.4.camel@localhost
Matthew Cline <matt@nightrealms•com> writes:
> When I try to a plain old "git add ." when files have been
> deleted/moved, I get the warning
>
>> You ran 'git add' with neither '-A (--all)' or '--ignore-removal'
>
> There should be some way to put something in ~/.gitconfig to tell git to
> always choose one or another.
The lack of configurability is very much deliberate.
Adding such knobs that make basic behaviour of Git different
depending on the per-user setting will make it unnecessarily harder
to run to help your coworker when she is having problems. "git add
directory" you type in her terminal during the session to help her
could work differently from the way you are used to, if we added
such a knob. We will not be making that mistake.
As the advice message says, "git add directory" ignores removed
files in the directory in the current version, and in Git 2.0, the
removals are recorded in the index with such a command, so that "add
directory" records the state of the directory as a whole to the
index, which is more consistent.
And that works for everybody the same way; the only way to prepare
for you not to be negatively affected by the switchover is to train
your fingers to say --all or --ignore-removal when the difference in
behaviour in the current and future versions matters, hence this
advise.
next prev parent reply other threads:[~2013-10-16 21:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-25 4:01 Feature request: Config option for --no-ignore-removal/--ignore-removal Matthew Cline
2013-10-16 21:38 ` Junio C Hamano [this message]
2013-10-17 0:31 ` Felipe Contreras
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=xmqqli1s6gly.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=matt@nightrealms$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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