From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Erick Mattos <erick.mattos@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Re: [PATCH v3] git checkout -b: unparent the new branch with -o
Date: Tue, 16 Mar 2010 22:23:10 -0700 [thread overview]
Message-ID: <7v4okfiksh.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 20100317041307.GA26641@progeny.tock
Jonathan Nieder <jrnieder@gmail.com> writes:
> Junio was discussing the case B.
Well, not really. Even as an ingredient, "nuke index, leaving files in
the work tree around" is the most difficult-to-use mode of operation.
Either "try to run 'git rm -f .' from the toplevel and only if it succeeds
point HEAD to an unborn branch" (aka "remove both"), or "point HEAD to an
unborn branch without doing anything else" (aka "keep both") would be an
ingredient that is far easier to use.
next prev parent reply other threads:[~2010-03-17 5:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-16 18:19 [PATCH v3] git checkout -b: unparent the new branch with -o Erick Mattos
2010-03-16 22:56 ` Junio C Hamano
2010-03-17 1:10 ` Erick Mattos
2010-03-17 4:13 ` Jonathan Nieder
2010-03-17 5:23 ` Junio C Hamano [this message]
2010-03-17 6:40 ` Jonathan Nieder
2010-03-17 17:17 ` Junio C Hamano
2010-03-17 18:55 ` Erick Mattos
2010-03-17 5:21 ` Junio C Hamano
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=7v4okfiksh.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@gmail.com \
/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).