Re: Better cooperation between checkouts and stashing
- From
- Markus Elfring <markus.elfring@web.de>
- Date
- Mar 1, 2010, 10:50 UTC
- Message-ID
- <4B8B9BF1.10408@web.de>
- In-Reply-To
- <7vr5o6s5xf.fsf@alter.siamese.dyndns.org>
Show 7 quoted lines
> - The branch you happen to have checked out was 'next', but the solution > is a bugfix, and should go to 'maint'. > > Now, at this point, you want to checkout 'maint' without losing your local > change. The paths you touched with your quick fix are often not different > between the two branches, and "checkout maint" will checkout the branch > while keeping your local changes intact.
Does the wording in the manual fit to the mentioned software development practice?
"When <paths> are not given, this command switches branches by updating the index, working tree, and HEAD to reflect the specified branch."
I see a need for further clarifications of the involved details. - Only the focus will be set on the specified branch. - Would it be useful if it will become configurable if the corresponding contents will also be automatically restored by a checkout?
Regards, Markus