From: Philip Oakley <philipoakley@iee.email>
To: Tom Miller <jackerran@gmail.com>, git@vger.kernel.org
Subject: Re: Propose promoting 'contrib/rerere-train.sh' to command
Date: Sat, 21 Dec 2019 17:00:48 +0000 [thread overview]
Message-ID: <7b60ce55-700e-0c67-76ac-a983991e49f2@iee.email> (raw)
In-Reply-To: <BZAQIE4YND2I.Z7BFCW7BLH3K@penguin>
Hi Tom,
On 21/12/2019 02:17, Tom Miller wrote:
> I would like to propose promoting 'contrib/rerere-train.sh' to one of the
> following:
>
> 1. A builtin c command 'builtin/rerere-train.c'
> 2. To the top level directory as a built in script 'git-rerere-train.sh'
>
> I have recently found myself writing scripts using 'contrib/rerere-train.sh'
> and I wish it was built into the command. This would make it easier to use
> rather than having to find it on different platforms. I think it could also
> benefit from some documentation.
>
> I am trying to gauge the interest in this change before spending some time on
> working on it. I would also appreciate feedback or alternative approaches to
> what I have suggested. Thank you for your time.
>
> Thanks,
> Tom Miller
This sounds like a useful capability (especially the documentation!).
I also had aspirations that there should also be a way of exchanging the
essence of the rerere data when conflicts (e.g. feature vs master branch
merges) are known locally and ought to be communicable with the patch sets.
see messages:
<37ccaad0-40b4-ca63-e057-791119d7fa69@talktalk.net>
<nycvar.QRO.7.76.6.1909261253400.15067@tvgsbejvaqbjf.bet>
Philip
next prev parent reply other threads:[~2019-12-21 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-21 2:17 Propose promoting 'contrib/rerere-train.sh' to command Tom Miller
2019-12-21 17:00 ` Philip Oakley [this message]
2019-12-21 17:37 ` Philip Oakley
2019-12-21 19:31 ` Jeff King
2019-12-21 23:52 ` Junio C Hamano
2019-12-22 7:58 ` Jeff King
2019-12-22 13:14 ` Tom Miller
2020-01-01 22:06 ` Johannes Schindelin
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=7b60ce55-700e-0c67-76ac-a983991e49f2@iee.email \
--to=philipoakley@iee.email \
--cc=git@vger.kernel.org \
--cc=jackerran@gmail.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).