Re: [PATCH 1/2] Allow users to require source branch on git-checkout -b.

From: Shawn Pearce <spearce@spearce.org>
Date: Dec 8, 2006, 05:59 UTC
Message-ID: <20061208055938.GB13999@spearce.org>
In-Reply-To: <20061208044516.GC5939@fieldses.org>

"J. Bruce Fields" <bfields@fieldses.org> wrote:

Show 8 quoted lines

> On Thu, Dec 07, 2006 at 04:59:14PM -0500, Shawn Pearce wrote:
> > I'm seeing bad branches all to often with some of the folks I have
> > to work with.  They apparently have been unable to learn the new
> > trick of either remembering what branch they are currently on and
> > what changes it has, or to always supply the branch they want to
> > start from with their new branch.
> 
> Would the trick of putting the branch name in the shell prompt work?

Its in the prompt for all of these users; I forced it in as part of
the system's /etc/profile.d.  They just forget that they should think
about where they should start their branch from before they make it.

Show 5 quoted lines

> But my main complaint is just that I wouldn't want to see the behavior
> of defaulting to HEAD--behavior which is simple, easy to explain, and
> shared by most other git commands--by something significantly more
> complicated.  That's more a complaint about Junio's suggestion than
> yours, though.

True, defaulting to HEAD is something that is done almost everywhere. Changing it for `git checkout -b` may surprise a lot of people, almost as much as --index vs. --cached.

Maybe what I should do is stop whining about the command line Porcelain-ish and get branch controls working in git-gui. Then I can take away the command line from these users who are causing me so much grief.