From: Denton Liu <liu.denton@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: Eric Sunshine <sunshine@sunshineco.com>,
Junio C Hamano <gitster@pobox.com>
Subject: [PATCH v3 0/2] allow checkout and branch to create branches on a merge base
Date: Sat, 27 Apr 2019 05:02:16 -0700 [thread overview]
Message-ID: <cover.1556366347.git.liu.denton@gmail.com> (raw)
In-Reply-To: <cover.1556305561.git.liu.denton@gmail.com>
Thanks again for the review, Junio.
I've squashed 2/3 and 3/3 together and made that documentation change I
was talking about earlier.
---
Changes since v2:
* Squashed 2/3 with 3/3
* Document merge base syntax for <start_point> in git-checkout.txt
Changes since v1:
* Moved multiple `test_when_finished` calls that appeared in "reverse
order" into one call that appears in the logical order
* Made create_branch handle merge base revs instead of putting a hack
into checkout
Denton Liu (2):
t2018: cleanup in current test
branch: make create_branch accept a merge base rev
Documentation/git-branch.txt | 6 +++-
Documentation/git-checkout.txt | 4 +++
branch.c | 2 +-
t/t2018-checkout-branch.sh | 56 ++++++++++++++++++----------------
t/t3200-branch.sh | 14 ++++++---
5 files changed, 50 insertions(+), 32 deletions(-)
Range-diff against v2:
1: 9d04faf29d = 1: 9d04faf29d t2018: cleanup in current test
2: 5e8320cd80 < -: ---------- t2018: demonstrate checkout -b merge base bug
3: c91c7535a7 ! 2: bb25852740 branch: make create_branch accept a merge base rev
@@ -41,6 +41,21 @@
Note that this will create the new branch, but it will not switch the
working tree to it; use "git checkout <newbranch>" to switch to the
+ diff --git a/Documentation/git-checkout.txt b/Documentation/git-checkout.txt
+ --- a/Documentation/git-checkout.txt
+ +++ b/Documentation/git-checkout.txt
+@@
+ <start_point>::
+ The name of a commit at which to start the new branch; see
+ linkgit:git-branch[1] for details. Defaults to HEAD.
+++
++As a special case, you may use `"A...B"` as a shortcut for the
++merge base of `A` and `B` if there is exactly one merge base. You can
++leave out at most one of `A` and `B`, in which case it defaults to `HEAD`.
+
+ <tree-ish>::
+ Tree to checkout from (when paths are given). If not specified,
+
diff --git a/branch.c b/branch.c
--- a/branch.c
+++ b/branch.c
@@ -61,20 +76,29 @@
do_checkout branch2
'
--test_expect_failure 'checkout -b to a merge base' '
+test_expect_success 'checkout -b to a merge base' '
++ test_when_finished "
++ git checkout branch1 &&
++ test_might_fail git branch -D branch2" &&
++ git checkout -b branch2 branch1...
++'
++
+ test_expect_success 'checkout -b to a new branch, set to an explicit ref' '
test_when_finished "
git checkout branch1 &&
- test_might_fail git branch -D branch2" &&
@@
do_checkout branch2 "" -B
'
--test_expect_failure 'checkout -B to a merge base' '
+test_expect_success 'checkout -B to a merge base' '
- git checkout branch1 &&
++ git checkout branch1 &&
++
++ git checkout -B branch2 branch1...
++'
++
+ test_expect_success 'checkout -B to an existing branch from detached HEAD resets branch to HEAD' '
+ git checkout $(git rev-parse --verify HEAD) &&
- git checkout -B branch2 branch1...
diff --git a/t/t3200-branch.sh b/t/t3200-branch.sh
--- a/t/t3200-branch.sh
--
2.21.0.1000.g11cd861522
next prev parent reply other threads:[~2019-04-27 12:02 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-25 21:10 [PATCH 0/3] checkout: allow -b/-B to work on a merge base Denton Liu
2019-04-25 21:10 ` [PATCH 1/3] t2018: cleanup in current test Denton Liu
2019-04-25 22:34 ` Eric Sunshine
2019-04-26 0:40 ` Denton Liu
2019-04-26 2:50 ` Junio C Hamano
2019-04-26 6:58 ` Eric Sunshine
2019-04-25 21:10 ` [PATCH 2/3] t2018: demonstrate checkout -b merge base bug Denton Liu
2019-04-25 21:10 ` [PATCH 3/3] checkout: allow -b/-B to work on a merge base Denton Liu
2019-04-26 3:02 ` Junio C Hamano
2019-04-26 4:59 ` Junio C Hamano
2019-04-26 19:21 ` [PATCH v2 0/3] allow checkout and branch to create branches " Denton Liu
2019-04-26 19:21 ` [PATCH v2 1/3] t2018: cleanup in current test Denton Liu
2019-04-26 19:21 ` [PATCH v2 2/3] t2018: demonstrate checkout -b merge base bug Denton Liu
2019-04-26 19:21 ` [PATCH v2 3/3] branch: make create_branch accept a merge base rev Denton Liu
2019-04-26 23:07 ` [PATCH v2 0/3] allow checkout and branch to create branches on a merge base Junio C Hamano
2019-04-26 23:40 ` Denton Liu
2019-04-26 23:52 ` Denton Liu
2019-04-27 0:01 ` Junio C Hamano
2019-04-27 12:02 ` Denton Liu [this message]
2019-04-27 12:02 ` [PATCH v3 1/2] t2018: cleanup in current test Denton Liu
2019-04-27 12:02 ` [PATCH v3 2/2] branch: make create_branch accept a merge base rev Denton Liu
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=cover.1556366347.git.liu.denton@gmail.com \
--to=liu.denton@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).