|
From: | Dmitry Gutov |
Subject: | bug#20292: 24.5; Saving Git-controlled file with merge conflicts after "stash pop" stages the file |
Date: | Sun, 19 Apr 2015 21:11:49 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Thunderbird/36.0 |
On 04/19/2015 09:05 PM, Eli Zaretskii wrote:
I was talking about the following simple scenatio: git pull # get an error about uncommitted changes that prevent merge git stash save git pull git stash pop # get an error message about conflicts # resolve conflicts and save de-conflicted files
And I, about a related but slightly different one, which we'd prefer not to make worse, right?
# edit foo.bar git stash save # edit foo.bar again, differently, maybe in several places git add foo.bar git stash pop # get an error message about conflict in foo.bar # resolve conflicts and save foo.bar
[Prev in Thread] | Current Thread | [Next in Thread] |