All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Schwarz <simonschwarzcor@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Patch submission process question
Date: Wed, 17 Aug 2011 10:35:11 +0200	[thread overview]
Message-ID: <4E4B7D3F.1010809@gmail.com> (raw)
In-Reply-To: <4E4AA147.2050602@freescale.com>

On 08/16/2011 06:56 PM, Scott Wood wrote:
<snip>
>>> How about a patch that was sent, that at the time didn't depend on
>>> another series, but after review and changes, now depends on those
>>> changes?
>> Then you have to note it in the version history that it now depends on
>> another patch - don't forget to also note it in the normal merge message.
>
> Merge message?  If you mean the commit message (above the "---"), why?
> It should not be committed before its dependencies.
Sorry meant commit message. True - so just note it in the version 
history and - for convenience - in the cover letter?

Regards
Simon

      parent reply	other threads:[~2011-08-17  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-16  1:20 [U-Boot] Patch submission process question Joe Hershberger
2011-08-16  7:06 ` Simon Schwarz
2011-08-16 16:56   ` Scott Wood
2011-08-16 22:31     ` Joe Hershberger
2011-08-17  8:35     ` Simon Schwarz [this message]

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=4E4B7D3F.1010809@gmail.com \
    --to=simonschwarzcor@googlemail.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.