On Thu, Oct 30, 2008 at 02:28:35PM -0400, Nicolas Pitre wrote:
> > It's not about magic, it's about sensible defaults. Currently this use
> > case is an error, and the resultant command is very long to type, and
> > involves typing the branch name twice. I end up writing things like:
> >
> > git checkout -b {,origin/}wr34251-do-something
> >
> > For the user who doesn't know to use the ksh-style {} blocks this is
> > voodoo. The longer form is cumbersome.
>
> This is no excuse for promoting semantics only useful in such special
> cases.
It is really not so rare to have an upstream repo with branches such
as "stable", "next" and the like. This syntax extension would make is
as straightforward to work on "stable" as it is on remote HEAD
(usually master, which has already been magically setup for you).
BTW this use case reminds me that the remote HEAD has its own special
treatment for "clone", which AFAIK cannot be overriden from
command-line (I still sometimes lack what cogito provided as "cg clone
URL#branch").
> As long as it checks it out with a detached head if it is a remote
> branch then I have no issue.
Yes it is possible, but that does not necessarily make a UI
improvement worthless.
Best regards,
--
Yann
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
