Re: How to exchange rerere/redo resolutions?
- Date: Wed, 15 May 2019 00:11:09 +0100
- From: Philip Oakley <philipoakley@xxxxxxx>
- Subject: Re: How to exchange rerere/redo resolutions?
On 14/05/2019 09:21, Ævar Arnfjörð Bjarmason wrote:
Hmm, I'd now agree it's not a mistake, but the implementation detail is
historic. I've now found [1,2,3,4] from before I knew of Git! And it's
not mentioned in any of the documentation.
On Tue, May 14 2019, Philip Oakley wrote:
On 10/05/2019 15:59, Philip Oakley wrote:
You can publish your merged branch somewhere, and others can use
contrib/rerere-train.sh to learn from the resolution.
Supposedly, I've never actually used it...
Does the contrib/rerere-train.sh actually work? I'm reading the code
to ensure I understand what rerere/redo is doing, and in the training
it tries to detect MERGE_RR via L87
if test -s "$GIT_DIR/MERGE_RR"
It's not clear if that is an internal implementation detail, or a
mistaken use of a historic path name. Can anyone enlighten me?
Historic? No, this is path.c now on master:
Hopefully it'll be integrated into rerere/redo before that ;-), along
with a bit more documentation on the capability for those who arrived
late to the party. The use of this implementation detail came up
yesterday in .
Internal, sure. We don't document it so it could change in theory, but
then we'd probably change rerere-train.sh along with it...
The tricky part is when the patch series doesn't apply so the
conflict isn't yet on any branch..
When copying patches across to Git for Windows, the conflict
resolution can be tricky.
 git-rerere: reuse recorded resolve, 29 Jan 2006,
 StGIT and rerere, 26 Oct 2006,
 git-explain, 04 Dec 2006,
 Make git-rerere a builtin, 20 Dec 2006,
 merge: add --quit, 14 May 2019 ,