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 13:00:06 +0200 [thread overview]
Message-ID: <4E119D36.7040900@keymile.com> (raw)
Hi Wolfgang,
I have a short question about sending updated patch versions. I have read:
http://www.denx.de/wiki/view/U-Boot/Patches#Sending_updated_patch_versions
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.
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"
In the past I did this, but I ask myself if this is really needed.
Please let me know what the rules are in such a case. I think the wiki page did
not describe what to do with unchanged but version updated patches.
Best regards
Holger
next reply other threads:[~2011-07-04 11:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-04 11:00 Holger Brunck [this message]
2011-07-04 15:05 ` [U-Boot] sending updated patch versions Wolfgang Denk
2011-07-04 15:25 ` Holger Brunck
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=4E119D36.7040900@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.