Re: [PATCH v4 1/3] rebase: add documentation and test for --no-rebase-merges
- From
Alex Henrie <alexhenrie24@gmail.com>
- Date
- Feb 25, 2023, 18:09 UTC
- Message-ID
- <CAMMLpeTWsuEpC878BRh7zNZF_7pVZcaxw9A-bOwEOAPbH-rnOA@mail.gmail.com>
- In-Reply-To
- <f1e8b718-c54e-b228-860c-54d7defd9e7d@gmx.de>
On Fri, Feb 24, 2023 at 6:58 AM Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> On Thu, 23 Feb 2023, Junio C Hamano wrote: > > > No cover letter to summarize the changes?
Show 8 quoted lines
> A range-diff would have been nice, too, as well as replying-to the > previous iteration so that they're all within the same email thread. > > And if you want cover letters and range-diffs and correct In-Reply-To > headers, I can think of a splendid way to encourage that: promote tools > that do that. That's much better than to require contributors to know all > the customs and conventions of the project and send mails in the exact > desired format...
It would also help if those expectations were mentioned in Documentation/SubmittingPatches. There's nothing in there about range-diff or In-Reply-To.
I think I followed all of the customs of the Git mailing list for v5. Please let me know if I missed something.
-Alex