Re: [PATCH 2/2] read-tree: at least one tree-ish argument is required
- From
Johannes Schindelin <johannes.schindelin@gmx.de>
- Date
- Dec 19, 2009, 10:56 UTC
- Message-ID
- <alpine.DEB.1.00.0912191155360.4985@pacific.mpi-cbg.de>
- In-Reply-To
- <7vfx77lg2s.fsf@alter.siamese.dyndns.org>
Hi,
On Fri, 18 Dec 2009, Junio C Hamano wrote:
Show 13 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > > > As read-tree is a very basic and low-level Porcelain, if somebody were > > using it to empty the index in an existing script, this change would > > appear as a regression and hopefully will be caught eventually, and > > updating such a script can be made reasonably easy if we want to be > > helpful (the error message can suggest running "rm $GIT_DIR/index", > > for example). > > IOW, I would prefer to queue something like this in the upcoming > version, and then later make it die(). I do not think anybody relies on > it, but we have been wrong before. If the warning doesn't trigger for > anybody, that is also fine as well.
I fully expect it not to trigger for anybody (except maybe you, if you have hidden a script somewhere that uses read-tree to empty the index), because at least for this developer, the standard way of emptying the index is simply "rm .git/index".
Ciao, Dscho