Re: [PATCH 1/2] Allow users to require source branch on git-checkout -b.
- From
- J. Bruce Fields <bfields@fieldses.org>
- Date
- Dec 8, 2006, 04:45 UTC
- Message-ID
- <20061208044516.GC5939@fieldses.org>
- In-Reply-To
- <20061207215914.GC12502@spearce.org>
On Thu, Dec 07, 2006 at 04:59:14PM -0500, Shawn Pearce wrote:
Show 5 quoted lines
> 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.
Well, it's true that "git branch" is the first thing I type whenever I sit down, just to remember where I am....
Would the trick of putting the branch name in the shell prompt work?
Show 8 quoted lines
> Consequently they are cussing at Git rather often, as "this damn > Git crap always does the wrong with my files". Despite it being > their own fault for not thinking before doing... > > Of course many of these users also don't understand the value of a > good short diff for a simple change. *sigh* But right now I just > want to stop them from creating branches off the wrong branch point > 95% of the time.
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.