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: Tue, 16 Aug 2011 09:06:01 +0200	[thread overview]
Message-ID: <4E4A16D9.9050706@gmail.com> (raw)
In-Reply-To: <CANr=Z=aL2L39P+z3yjMw0HND5=UNT_0BExbqRX_z24zdjmzhmw@mail.gmail.com>

Hi Joe,

On 08/16/2011 03:20 AM, Joe Hershberger wrote:
> Hi u-boot,
>
> What is the recommended way to handle a patch series that depends on
> another patch series (already sent but not integrated)?
>
AFAIK the recommend way is to note in the patch that it depends on 
another - best with some kind of link from gmane or a message-ID.

> 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.

>
> Even a bit more generally, some of the series are getting quite long
> due to small dependencies.  This tends to put lots of unrelated
> content into the same series based on small dependencies.  How is this
> supposed to be dealt with?  Is it best to make long series or just to
> send part of it and wait for it to be integrated before sending the
> rest?
Hm, here U'am not really sure - I think I would send a complete series - 
but this is best answered by a custodian.

>
> Thanks,
> -Joe

Regards
Simon

  reply	other threads:[~2011-08-16  7:06 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 [this message]
2011-08-16 16:56   ` Scott Wood
2011-08-16 22:31     ` Joe Hershberger
2011-08-17  8:35     ` Simon Schwarz

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=4E4A16D9.9050706@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.