Re: [PATCH 1/5] port --ignore-unmatch to "git add"
- From
- Luke-Jr <luke@dashjr.org>
- Date
- Aug 14, 2009, 20:39 UTC
- Message-ID
- <200908141539.18087.luke@dashjr.org>
- In-Reply-To
- <7vws56i35q.fsf@alter.siamese.dyndns.org>
On Friday 14 August 2009 02:52:33 pm Junio C Hamano wrote:
Show 18 quoted lines
> Thomas Rast <trast@student.ethz.ch> writes: > > Junio C Hamano wrote: > >> Chould you refresh my memory a bit? > >> > >> In what circumstance is "rm --ignore-unmatch" useful to begin with? > > > > Not sure about add --ignore-unmatch myself, but there's even an > > example of rm --ignore-unmatch in man git-filter-branch, along the > > lines of > > > > git filter-branch --index-filter ' > > rm --ignore-unmach some_file_that_shouldnt_be_in_history > > ' -- --all > > Ah, that makes sense. I am not sure about "add --ignore-unmatch" myself > either, and an example similar to the above filter-branch would not apply > very easily (i.e. "add a file that should have been in history" would not > need --ignore-unmatch).
The purpose of "add --ignore-unmatch" is to ignore race conditions where one of the files to be added has been deleted after git is executed, but before git scans it.