From: Yann Dirson Date: Mon, 31 Aug 2009 08:16:34 GMT Subject: Re: [BUG] git stash refuses to save after "add -N" Message-ID: <51ce4af01c8de1adb66a1818baab1f8a.squirrel@intranet.linagora.com> In-Reply-To: <20090831050554.GA17197@coredump.intra.peff.net> > On Sun, Aug 30, 2009 at 10:03:07PM -0700, Junio C Hamano wrote: > >> > - "-f" is kind of vague. Would people expect it to force aspects of >> > the stash? Should it be "--intent-as-empty"? >> >> I am not sure if asking for positive confirmation with "-f" is even >> worth >> it. As you pointed out in your earlier message, which prompted me to >> respond with a patch, when this codepath is exercised, the user is in a >> rush, and I do not see what else the user would want to do other than >> including it in the stash by rerunning with -f. > > I guess it was just to mitigate my fear that we are somehow creating a > stash that will confuse people when they apply it. But really that fear > is probably unjustified. Well, indeed each time I use "add -N" it is mostly to get "git diff" show me the contents of the new file as part of my WIP, so it would not make much difference to me if "add -N" would just add the file as empty to the index in the first place. Out of curiosity, does anyone make any use of the current difference between not-added-yet and added-as-empty ?