Quick multiple-patch submission question

[Erich Hoover]

When submitting multiple patches that apply to the same component but
each patch is unrelated (ie. each one fixes a different issue), is it
still appropriate to label the patches with the [PATCH X/Y] notation?
In the case I have at hand the patches are even for different files of
the same component, so the apply order completely doesn't matter.

Erich Hoover
ehoover(a)mines.edu

[Juan Lang]

> When submitting multiple patches that apply to the same component but
> each patch is unrelated (ie. each one fixes a different issue), is it
> still appropriate to label the patches with the [PATCH X/Y] notation?
> In the case I have at hand the patches are even for different files of
> the same component, so the apply order completely doesn't matter.

In this case it's not needed.  I don't bother with the patch x/y
notation, others do.. either way is fine.
--Juan

[Henri Verbeet]

On 29 January 2010 00:28, Juan Lang <juan.lang(a)gmail.com> wrote:
> > When submitting multiple patches that apply to the same component but
> > each patch is unrelated (ie. each one fixes a different issue), is it
> > still appropriate to label the patches with the [PATCH X/Y] notation?
> > In the case I have at hand the patches are even for different files of
> > the same component, so the apply order completely doesn't matter.
>
> In this case it's not needed.  I don't bother with the patch x/y
> notation, others do.. either way is fine.
> Yeah. Note that git format-patch will create a series unless you tell
> it not to though, so at least in my case it's mostly a matter of not
> bothering with removing it. (And I guess on some level also confidence
> that the patches I'm sending are correct.)

[Michael Stefaniuc]

On 01/29/2010 12:26 AM, Erich Hoover wrote:
> When submitting multiple patches that apply to the same component but
> each patch is unrelated (ie. each one fixes a different issue), is it
> still appropriate to label the patches with the [PATCH X/Y] notation?
> In the case I have at hand the patches are even for different files of
> the same component, so the apply order completely doesn't matter.
> Then send them separately. That avoids having the rest of the patch 
> chain being blocked by a rejected patch further in the front of the chain.

bye
	michael