Re: [PATCH] cmd_reset: don't trash uncommitted changes unless told to

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Jun 25, 2008, 12:33 UTC
Message-ID: <alpine.DEB.1.00.0806251332190.9925@racer>
In-Reply-To: <20080625104605.GA10322@atn.sw.ru>

Hi,

On Wed, 25 Jun 2008, Anton Gladkov wrote:

Show 14 quoted lines

> 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:
> > > 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...

Actually, I don't find this a good reason at all. The fact that other SCMs bastardized a term to mean something it clearly does not mean, is irrelevant here.

The thing is: if we say "let's switch branches", what command would spring to mind to a (non-CVS-braindamaged) user? Exactly: "git branch". That is the command that should do something with branches.

Ciao, Dscho