Thread (22 messages) flat view 22 messages, 9 authors, 2016-06-15

Re: pull into dirty working tree

From: Linus Torvalds <torvalds@linux-foundation.org>
Date: 2016-06-15 22:43:16


On Thu, 14 Jun 2007, Olivier Galibert wrote:
On Thu, Jun 14, 2007 at 08:46:27AM -0700, Linus Torvalds wrote:
quoted
So it might be easier to take a "git stash ; git pull ; git unstash" 
approach instead of making "git pull" handle working tree conflicts 
itseld.
Isn't that "git add .; git commit; git fetch; git rebase <something>;
git reset ^HEAD"?  With the conflict resolution happening at rebase
time.
No.

The two workflows happen to co-incide *if* the "git pull" is a 
fast-forward, but not if you actually had previous commits that you 
wanted the "git pull" to merge.

So if you want things to actually work as a "git pull with dirty state 
merge", you really do need to do "git stash + git pull + git unstash".

		Linus
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help