From: Matthias Beyer <mail@beyermatthias.de>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Matthias Beyer <mail@beyermatthias.de>,
Konstantin Khomoutov <kostix@bswap.ru>,
Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: [PATCH v2] Add note that conflict resolution is still performed
Date: Fri, 15 Jul 2022 11:25:27 +0200 [thread overview]
Message-ID: <20220715092527.1567837-1-mail@beyermatthias.de> (raw)
In-Reply-To: <xmqq35f6fe0j.fsf@gitster.g>
We should note that conflict resolution is still performed, even if
`--no-rerere-autoupdate` is specified, to make sure users do not get
confused by the setting and assume this disables rerere conflict
resultion altogether.
CC: Phillip Wood <phillip.wood@dunelm.org.uk>
CC: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Matthias Beyer <mail@beyermatthias.de>
---
Documentation/git-cherry-pick.txt | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/git-cherry-pick.txt b/Documentation/git-cherry-pick.txt
index 78dcc9171f..b92aa1f9da 100644
--- a/Documentation/git-cherry-pick.txt
+++ b/Documentation/git-cherry-pick.txt
@@ -160,6 +160,10 @@ effect to your index in a row.
--no-rerere-autoupdate::
Allow the rerere mechanism to update the index with the
result of auto-conflict resolution if possible.
+ The `--no-rerere-autoupdate` option does not prevent the conflict
+ resolution, but prevents the index from being updated. This gives the
+ user a chance for a final sanity check before using linkgit:git-add[1]
+ to add the result.
SEQUENCER SUBCOMMANDS
---------------------
--
2.36.0
next parent reply other threads:[~2022-07-15 9:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <xmqq35f6fe0j.fsf@gitster.g>
2022-07-15 9:25 ` Matthias Beyer [this message]
2022-07-15 21:32 ` [PATCH v2] Add note that conflict resolution is still performed Junio C Hamano
2022-07-15 21:50 ` Junio C Hamano
2022-08-03 20:59 ` [PATCH] doc: clarify rerere-autoupdate 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=20220715092527.1567837-1-mail@beyermatthias.de \
--to=mail@beyermatthias.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kostix@bswap.ru \
--cc=phillip.wood@dunelm.org.uk \
/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).