# Feature request: Config option for --no-ignore-removal/--ignore-removal 3 messages from 2013-09-25 to 2013-10-17. Participants: Matthew Cline, Junio C Hamano, Felipe Contreras. Thread: https://gitlist.dev/t/35013 ## Matthew Cline, 2013-09-25 04:01 Subject: Feature request: Config option for --no-ignore-removal/--ignore-removal Message-ID: <1380081691.7963.4.camel@localhost> URL: https://gitlist.dev/e/1380081691.7963.4.camel%40localhost ``` 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. ``` ## Junio C Hamano, 2013-10-16 21:38 Subject: Re: Feature request: Config option for --no-ignore-removal/--ignore-removal Message-ID: URL: https://gitlist.dev/e/xmqqli1s6gly.fsf%40gitster.dls.corp.google.com In-Reply-To: <1380081691.7963.4.camel@localhost> ``` Matthew Cline 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. ``` ## Felipe Contreras, 2013-10-17 00:31 Subject: Re: Feature request: Config option for --no-ignore-removal/--ignore-removal Message-ID: <525f2ffe6790b_43dcf8be8485@nysa.notmuch> URL: https://gitlist.dev/e/525f2ffe6790b_43dcf8be8485%40nysa.notmuch In-Reply-To: ``` Junio C Hamano wrote: > Matthew Cline 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. That's going to happen regardless. You are assuming she is running Git v2.0, which she might not. -- Felipe Contreras ```