From mboxrd@z Thu Jan  1 00:00:00 1970
From: Simon Schwarz <simonschwarzcor@googlemail.com>
Date: Wed, 17 Aug 2011 10:35:11 +0200
Subject: [U-Boot] Patch submission process question
In-Reply-To: <4E4AA147.2050602@freescale.com>
References: <CANr=Z=aL2L39P+z3yjMw0HND5=UNT_0BExbqRX_z24zdjmzhmw@mail.gmail.com>
	<4E4A16D9.9050706@gmail.com> <4E4AA147.2050602@freescale.com>
Message-ID: <4E4B7D3F.1010809@gmail.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

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