Re: Git branches - confusing behavior

[Teemu Likonen <tlikonen@iki.fi>]

Dima Kagan wrote (2008-05-11 16:39 +0300):

> My proposed change shouldn't necessarily break the described workflow.
> Git can keep the current behavior for new branches, but automatically
> 'stash' the changes when checking-out an existing branch. At least
> having an optional parameter for "auto-stashing" will be nice.
> 
> What do you think of that?

With the fact that Git's branches are just pointers to a commit (and
therefore to a history) and that you can checkout anything that refers
to a commit (branches, tags, SHA1's, relative pointers like
HEAD@{30.minutes.ago}^2~3) I think such auto-stashing would be make
things pretty complicated and unintuitive in the big picture. The user
interface remains simpler if we just learn to use "git stash" to
temporarily put away changes in the index and the working directory when
we need to.