From: Junio C Hamano <gitster@pobox.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: "ZheNing Hu" <adlternative@gmail.com>,
"ZheNing Hu via GitGitGadget" <gitgitgadget@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Christian Couder" <christian.couder@gmail.com>,
"Hariom Verma" <hariom18599@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
"Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Eric Sunshine" <sunshine@sunshineco.com>
Subject: Re: [PATCH 2/2] checkout: introduce "--to-branch" option
Date: Mon, 13 Dec 2021 13:36:40 -0800 [thread overview]
Message-ID: <xmqqr1agb313.fsf@gitster.g> (raw)
In-Reply-To: <211213.86r1ag6ztx.gmgdl@evledraar.gmail.com> (=?utf-8?B?IsOG?= =?utf-8?B?dmFyIEFybmZqw7Zyw7A=?= Bjarmason"'s message of "Mon, 13 Dec 2021 20:55:00 +0100")
Ævar Arnfjörð Bjarmason <avarab@gmail.com> writes:
> I don't see how it's fundimentally different than the DWIM logic of
> taking "<name>" and seeing that there's only one "refs/heads/<name>",
> and giving up in other cases where we get ambiguous reference names that
> we can't resolve.
In that example, once you obtained a local branch whose name is
<name>, it is obvious how you would work with that. Your next "git
checkout <name>" would work on the local one, and only the initial
one does something magical.
Which makes quite a lot of sense.
There is no similarity in it with "--to-branch <tag>" that is being
discussed here.
next prev parent reply other threads:[~2021-12-13 21:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 6:22 [PATCH 0/2] checkout: introduce "--to-branch" option ZheNing Hu via GitGitGadget
2021-12-10 6:22 ` [PATCH 1/2] checkout: handling branch_info memory leak ZheNing Hu via GitGitGadget
2021-12-10 7:13 ` Ævar Arnfjörð Bjarmason
2021-12-10 6:22 ` [PATCH 2/2] checkout: introduce "--to-branch" option ZheNing Hu via GitGitGadget
2021-12-10 8:34 ` Christian Couder
2021-12-11 6:34 ` ZheNing Hu
2021-12-10 8:59 ` Ævar Arnfjörð Bjarmason
2021-12-11 7:11 ` ZheNing Hu
2021-12-10 11:51 ` Bagas Sanjaya
2021-12-11 7:12 ` ZheNing Hu
2021-12-10 22:14 ` Junio C Hamano
2021-12-11 7:51 ` ZheNing Hu
2021-12-12 18:46 ` Junio C Hamano
2021-12-13 19:55 ` Ævar Arnfjörð Bjarmason
2021-12-13 21:36 ` Junio C Hamano [this message]
2021-12-13 21:52 ` 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=xmqqr1agb313.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=adlternative@gmail.com \
--cc=avarab@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@gmail.com \
--cc=hariom18599@gmail.com \
--cc=pclouds@gmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=sunshine@sunshineco.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.