Re: [PATCH] Documentation: add a planning document for the next CLI revamp

!MAILaRCHIVE_VOTE_RePLACE
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: Nicolas Pitre <nico@...>
Cc: Pierre Habouzit <madcoder@...>, Mike Hommey <mh@...>, Shawn O. Pearce <spearce@...>, <git@...>
Date: Thursday, October 30, 2008 - 7:28 pm

On Thu, 2008-10-30 at 14:28 -0400, Nicolas Pitre wrote:

Absolutely - if you've already got a branch "master", then
"git checkout master" should definitely give it to you.  If you go
"git checkout origin/master", you get a floating head.  But I quite often
find myself wanting to check out a remote branch, and give it a name just
like on the remote.  I want "git checkout blah" to assume that's
what I mean, until I make a local branch "blah".


Right - 'master' in this case resolves to something.  The ambiguity is
resolved by defaulting to the thing that resolves.  The fall-back
behaviour is only triggered if you asked for something that is currently
an error.  Because breaking expectations sucks.

Sam.

--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
Re: [PATCH] Documentation: add a planning document for the n..., Andreas Ericsson, (Thu Oct 30, 11:02 am)
Re: [PATCH] Documentation: add a planning document for the n..., Johannes Schindelin, (Fri Oct 31, 8:37 pm)
Re: [PATCH] Documentation: add a planning document for the n..., Sam Vilain, (Thu Oct 30, 7:28 pm)