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: Thu, 7 Dec 2006 16:40:53 -0500 [thread overview]
Message-ID: <20061207214053.GC31035@fieldses.org> (raw)
In-Reply-To: <7v64cns8nf.fsf@assigned-by-dhcp.cox.net>
On Thu, Dec 07, 2006 at 01:23:00PM -0800, Junio C Hamano wrote:
> Under my suggestion, the new git-checkout -b (and git-branch)
> would:
>
> (0) proceed if there is an explicit branch point specified on
> the command like, just like now;
>
> (1) allow omission of branch-point if the current branch has
> allowbranchbydefault configuration set as in above. A new
> branch is created forking off of the current HEAD;
>
> (2) allow omission of branch-point if no branch has such
> configuration; in other words, existing repositories that
> do not have the allowbranchbydefault configuration anywhere
> are not affected. A new branch is created forking off of
> the current HEAD;
>
> (3) otherwise, it barfs if you do not give an explicit
> branch-point.
>
> and a newly created repository that is newbie friendly has one
> such configuration automatically set for 'master' (if created
> with git-init) or whatever the primary branch is (if created
> with git-clone).
That makes the default behavior more complicated to explain. Is there
really sufficient evidence that this a serious problem?
next prev parent reply other threads:[~2006-12-07 21:41 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 [this message]
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
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=20061207214053.GC31035@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).