All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow users to require source branch on git-checkout -b.
Date: Thu, 7 Dec 2006 23:45:16 -0500	[thread overview]
Message-ID: <20061208044516.GC5939@fieldses.org> (raw)
In-Reply-To: <20061207215914.GC12502@spearce.org>

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.

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?

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


  reply	other threads:[~2006-12-08  4:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 10:01 [PATCH 1/2] Allow users to require source branch on git-checkout -b Shawn O. Pearce
2006-12-07 19:48 ` Junio C Hamano
2006-12-07 19:57   ` Shawn Pearce
2006-12-07 21:23     ` Junio C Hamano
2006-12-07 21:40       ` J. Bruce Fields
2006-12-07 21:59         ` Shawn Pearce
2006-12-08  4:45           ` J. Bruce Fields [this message]
2006-12-08  5:59             ` Shawn Pearce
2006-12-08  6:08               ` J. Bruce Fields
2006-12-08  6:19                 ` Shawn Pearce
2006-12-08  6:31               ` Junio C Hamano
2006-12-08 15:39                 ` J. Bruce Fields

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20061208044516.GC5939@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=spearce@spearce.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.