From: Holger Brunck <holger.brunck@keymile.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] sending updated patch versions
Date: Mon, 04 Jul 2011 17:25:08 +0200 [thread overview]
Message-ID: <4E11DB54.9000000@keymile.com> (raw)
In-Reply-To: <20110704150528.9C29015794D5@gemini.denx.de>
Hi,
On 07/04/2011 05:05 PM, Wolfgang Denk wrote:
> In message <4E119D36.7040900@keymile.com> you wrote:
>>
>> and I wonder if it is needed to update the history of *all* patches in a serie
>> even if for different specific patches nothing was changed. Or if it sufficient
>> if only the subject indicates the version number for such patches.
>
> If you keep the threading of the messages intact (i. e. supply proper
> In-reply-to: and References: headers - like you get automatically when
> inserting the message ID when "git send-email" asks for the
> "Message-ID to be used as In-Reply-To for the first email"), then
> there is usually no need to resend unchanged patces at all - what for?
> It would be just a waste of effort and bandwidth.
>
yes I agree and thats why I am asking. Ah ok, yes I have seen the message from
git send-email but wasn't sure how to use this.
So if I get a request to update 4/5 from a already posted patch serie which
message id I have to enter for "In-Reply-To for the first email"? I assume I
have to use the message id from the initial 4/5 Patch Email which has hit the
mailing list or?
>> E.g patch serie where only 1 patch has changes requested, do I need to update
>> all other patches with the history:
>>
>> "Changes for v2: - nothing"
>
> No. Please don't repost the unchanged patches at all. Repost just the
> one that you modified.
>
yes this sounds reasonable and is also less work for the sender.
Best regards
Holger Brunck
next prev parent reply other threads:[~2011-07-04 15:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 11:00 [U-Boot] sending updated patch versions Holger Brunck
2011-07-04 15:05 ` Wolfgang Denk
2011-07-04 15:25 ` Holger Brunck [this message]
2011-07-04 15:46 ` Wolfgang Denk
2011-07-05 19:25 ` Scott Wood
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=4E11DB54.9000000@keymile.com \
--to=holger.brunck@keymile.com \
--cc=u-boot@lists.denx.de \
/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