Re: Data Integrity & un-Commited Branches

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 15, 2007, 06:37 UTC
Message-ID: <7vk5qs8me5.fsf@gitster.siamese.dyndns.org>
In-Reply-To: <2a8a071a0709142324i29a863b7x8c164a589c1f1f9a@mail.gmail.com>

"Brian Scott Dobrovodsky" <brian@pontech.com> writes:

Show 7 quoted lines

>> It isn't unreasonable to want Git to save uncommitted work for the
>> current branch and then you switch to another, ending up with a
>> clean working directory when you finally get there.  Today we have
>> git-stash to help you with this, but I'm thinking maybe we want to
>> connect git-checkout with it?
>
> That would be great as a default action when using checkout!

I would not bet you will stay feeling that way as you gain experience. With "git stash create" (will be in 'next' this weekend), we could start using stashes more transparently from other commands, but I do not think this will ever become the default for branch switching, while I do not oppose to have such an option.