From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Shawn Pearce <spearce@spearce.org>, git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow users to require source branch on git-checkout -b.
Date: Fri, 8 Dec 2006 10:39:31 -0500 [thread overview]
Message-ID: <20061208153931.GA14378@fieldses.org> (raw)
In-Reply-To: <7vac1yoq3r.fsf@assigned-by-dhcp.cox.net>
On Thu, Dec 07, 2006 at 10:31:52PM -0800, Junio C Hamano wrote:
> Shawn Pearce <spearce@spearce.org> writes:
>
> >> 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.
>
> I did not mean to change the default to something other than
> HEAD depending on the configuration.
Right, I understand that behavior in existing repositories is not
changed...
> > (3) otherwise, it barfs if you do not give an explicit
> > branch-point.
>
> ... but a newly created repositories would have an
> allowbranchbydefault entry on "master" (and only on "master"),
> which means new people would be prevented from making mistakes
> when on a non-master branch 'foo':
... my concern is the default behavior on newly created repositories,
which (unless I've misunderstood) would become more complicated.
> But I do not deeply care about this.
OK. Me neither, to be honest.
prev parent reply other threads:[~2006-12-08 15:39 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
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 [this message]
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=20061208153931.GA14378@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.