All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kevin Daudt <me@ikke.info>
To: "Randall S. Becker" <rsbecker@nexbridge.com>
Cc: 'COLLOMB Joris -EXT' <joris.collomb-ext@alstomgroup.com>,
	git@vger.kernel.org
Subject: Re: Git checkout multiple options issue
Date: Mon, 28 Jan 2019 17:55:15 +0100	[thread overview]
Message-ID: <20190128165515.GA25995@alpha> (raw)
In-Reply-To: <000701d4b71c$f3ba57f0$db2f07d0$@nexbridge.com>

On Mon, Jan 28, 2019 at 10:20:02AM -0500, Randall S. Becker wrote:
> On January 28, 2019 9:25, COLLOMB Joris wrote:
> > -----Message d'origine-----
> >> De : Randall S. Becker <rsbecker@nexbridge.com> Envoyé : lundi 28 janvier
> >> 2019 15:12 À : COLLOMB Joris -EXT <joris.collomb-ext@alstomgroup.com>;
> >> git@vger.kernel.org Objet : RE: Git checkout multiple options issue
> >> 
> >> On January 28, 2019 8:25, COLLOMB Joris wrote:
> >> > git checkout -fb "branch_name"
> >> > (force branch creation and checkout it)
> >> >
> >> > doesn't work (even if option a separated).
> >> >
> >> > I don't know if this is consider as an issue, but here it is.
> >> 
> >> I think you might mean (which works on every platform I have):
> >> 
> >> git checkout -f -b "branch_name"
> >> 
> >> There is no provision for aggregating options into one. -fb (invalid) is
> not the
> >> same as -f -b (valid).
> 
> > git checkout -f -b "branch_name"
> > gives me " Fatal: A branch named 'branch_name' already exists."
> 
> Once the branch is created, you can't force its creation, because it is
> already created. Just
> 
> git checkout "branch_name"
> 
> is sufficient at this point. git is correct to complain that you are trying
> to create a branch that already exists.

git checkout -B exists, which does exactly that: force create a branch
at a new positon if it already exists.

Kind regards, Kevin

  parent reply	other threads:[~2019-01-28 16:55 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-28 13:25 Git checkout multiple options issue COLLOMB Joris -EXT
2019-01-28 14:12 ` Randall S. Becker
2019-01-28 14:24   ` COLLOMB Joris -EXT
2019-01-28 15:20     ` Randall S. Becker
2019-01-28 16:02       ` COLLOMB Joris -EXT
2019-01-28 16:37         ` Randall S. Becker
2019-01-28 16:55       ` Kevin Daudt [this message]
2019-01-28 17:29         ` 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=20190128165515.GA25995@alpha \
    --to=me@ikke.info \
    --cc=git@vger.kernel.org \
    --cc=joris.collomb-ext@alstomgroup.com \
    --cc=rsbecker@nexbridge.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 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.