From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: "Alex Henrie" <alexhenrie24@gmail.com>,
"Git mailing list" <git@vger.kernel.org>,
"Son Luong Ngoc" <sluongng@gmail.com>,
"Matthias Baumgarten" <matthias.baumgarten@aixigo.com>,
"Eric Sunshine" <sunshine@sunshineco.com>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Johannes Schindelin" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH] pull: don't say that merge is "the default strategy"
Date: Fri, 19 Nov 2021 09:16:48 -0800 [thread overview]
Message-ID: <xmqq7dd4qd4v.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BHAqhpK4F2wTRhxZ5DXKOJExMxihbdpx1d2fYqAgtzS9w@mail.gmail.com> (Elijah Newren's message of "Thu, 18 Nov 2021 21:41:22 -0800")
Elijah Newren <newren@gmail.com> writes:
>> I was referring to the patch that I originally wrote, before Elijah
>> made the changes that actually got the patch accepted:
>> https://lore.kernel.org/git/20210627000855.530985-1-alexhenrie24@gmail.com/
Ah, with that URL, the extra paragraph would have made sense. Here
is how amended the log message with this new information.
Thanks, all.
----- >8 --------- >8 --------- >8 --------- >8 -----
From: Alex Henrie <alexhenrie24@gmail.com>
Date: Thu, 18 Nov 2021 08:43:17 -0700
Subject: [PATCH] pull: don't say that merge is "the default strategy"
Git no longer has a default strategy for reconciling divergent branches,
because there's no way for Git to know which strategy is appropriate in
any particular situation.
The initially proposed version in [*], that eventually became
031e2f7a (pull: abort by default when fast-forwarding is not
possible, 2021-07-22), dropped this phrase from the message, but
it was left in the final version by accident.
* https://lore.kernel.org/git/20210627000855.530985-1-alexhenrie24@gmail.com/
Signed-off-by: Alex Henrie <alexhenrie24@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
---
builtin/pull.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/builtin/pull.c b/builtin/pull.c
index b311ea6b9d..20b585a76b 100644
--- a/builtin/pull.c
+++ b/builtin/pull.c
@@ -939,7 +939,7 @@ static void show_advice_pull_non_ff(void)
"You can do so by running one of the following commands sometime before\n"
"your next pull:\n"
"\n"
- " git config pull.rebase false # merge (the default strategy)\n"
+ " git config pull.rebase false # merge\n"
" git config pull.rebase true # rebase\n"
" git config pull.ff only # fast-forward only\n"
"\n"
--
2.34.0-202-gd9146917d7
prev parent reply other threads:[~2021-11-19 17:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 15:43 [PATCH] pull: don't say that merge is "the default strategy" Alex Henrie
2021-11-18 21:30 ` Junio C Hamano
2021-11-18 21:40 ` Alex Henrie
2021-11-19 5:41 ` Elijah Newren
2021-11-19 17:16 ` Junio C Hamano [this message]
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=xmqq7dd4qd4v.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=alexhenrie24@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=matthias.baumgarten@aixigo.com \
--cc=newren@gmail.com \
--cc=sluongng@gmail.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.
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.