From: Andrew Kreimer <algonell@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] Documentation/config: fix typos
Date: Mon, 23 Sep 2024 23:01:19 +0300 [thread overview]
Message-ID: <ZvHJD73k_SETqAsu@void.void> (raw)
In-Reply-To: <CAPig+cR5BdfVRwdXJ7viJbvgkUW7KStG2Y_=qGNzoXWrOgZcJg@mail.gmail.com>
On Mon, Sep 23, 2024 at 01:59:16PM -0400, Eric Sunshine wrote:
> On Mon, Sep 23, 2024 at 1:51 PM Eric Sunshine <sunshine@sunshineco.com> wrote:
> > Thanks. The changes in v2 of this series look fine.
> >
> > In the future, to make life easier for reviewers, when rerolling a
> > patch series, please include a cover letter ("git format-patch
> > --cover-letter") and include the following in the cover letter:
> >
> > * explain in your own words how the new version of the series differs
> > from the previous version
> >
> > * provide a link to the cover-letter of the previous version (i.e.
> > https://lore.kernel.org/git/20240920082815.8192-1-algonell@gmail.com/)
> >
> > * include a range-diff ("git format-patch --range-diff=") which
> > provides a mechanical representation of the differences between the
> > new version of the series and the previous version
>
> I forgot to mention email threading as a way to further help reviewers
> and readers of the mailing list archive...
>
> When sending a reroll of a series, use "git send-email --reply-to=" to
> reference the cover letter of the previous version. If your email
> client doesn't provide an easy way to access the ID of the previous
> cover letter, you can grab it from the list archive. For instance,
> consulting the above link:
>
> git send-email --reply-to='20240920082815.8192-1-algonell@gmail.com' ...
All noted, thank you!
next prev parent reply other threads:[~2024-09-23 20:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-23 11:03 [PATCH v2 1/2] Documentation/config: fix typos Andrew Kreimer
2024-09-23 11:03 ` [PATCH v2 2/2] Documentation: " Andrew Kreimer
2024-09-23 17:51 ` [PATCH v2 1/2] Documentation/config: " Eric Sunshine
2024-09-23 17:59 ` Eric Sunshine
2024-09-23 20:01 ` Andrew Kreimer [this message]
2024-09-23 18:43 ` Kristoffer Haugsbakk
2024-09-23 19:05 ` Eric Sunshine
2024-09-23 19:13 ` Kristoffer Haugsbakk
2024-11-25 20:20 ` Kristoffer Haugsbakk
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=ZvHJD73k_SETqAsu@void.void \
--to=algonell@gmail.com \
--cc=git@vger.kernel.org \
--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 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).