Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to
From: Anton Gladkov <hidden>
Date: 2016-06-15 22:44:49
Possibly related (same subject, not in this thread)
- 2016-06-15 · Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to · しらいしななこ <hidden>
- 2016-06-15 · Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to · しらいしななこ <hidden>
- 2016-06-15 · Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to · Junio C Hamano <hidden>
- 2016-06-15 · Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to · Avery Pennarun <hidden>
- 2016-06-15 · Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to · Theodore Tso <tytso@mit.edu>
On Wed, Jun 25, 2008 at 02:24:58PM +0400, Matthias Kestenholz wrote:
On Wed, 2008-06-25 at 11:16 +0100, Johannes Schindelin wrote:quoted
Incidentally, a friend just told me that "checkout" is everything but intuitive, and he would have preferred "git branch switch <branch>", but then settled for my proposed "git branch --switch <branch>", which I did not have time to implement yet, unfortunately.But why? I don't want to 'branch', I want to 'checkout' another branch, which incidentally matches the git command I need to use to achieve that.
Because 'checkout' in other SCMs like CVS or SVN means 'get latest data from repo', i.e. it acts like 'pull' or 'fetch' in git. And 'branch' means branch manipulation: creating, deleting, switching... -- Best regards, Anton mailto:agladkov@parallels.com