Re: git merge --abort deletes unstaged files
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 15, 2014, 22:02 UTC
- Message-ID
- <CAPc5daW5XejS7JFmQagOwgqSxS=subdJyCbM3JL2fa=4RmYsEg@mail.gmail.com>
- In-Reply-To
- <87iokolfc9.fsf@igel.home>
On Mon, Sep 15, 2014 at 2:54 PM, Andreas Schwab <schwab@linux-m68k.org> wrote:
Show 17 quoted lines
> Junio C Hamano <gitster@pobox.com> writes: > >> Andreas Schwab <schwab@linux-m68k.org> writes: >> >>> André Hänsel <andre@webkr.de> writes: >>> >>>> I ran git merge to merge a branch. There were some conflicted files. >>>> Although they were automatically resolved by git rerere, I still had to add >>>> them. >>> >>> If you want them to be added automatically, set rerere.autoupdate=true. >> >> I would have to caution against doing so without thinking, though. >> In other words, it is OK if you are Andreas who knows what he is >> doing, but it is not a very good advice to give to random newbies. > > If you are used to doing "git add ." afterwards it can't be much worse.
The right response to such a user would be to teach "add -u", or better yet to teach to use "add" on individual files as they are examined, no?