Hi Greg,
On Wed, 26 Jan 2011 08:22:23 +0100, Arend van Spriel <arend@xxxxxxxxxxxx>
wrote:
Hi Greg,
For the first patch your reply contained the question whether it should
be in the final .38 release. We are getting confused over here about the
distribution of patches in branches/repositories within the community so
could you elaborate a little and answer my questions below.
1. From the various response I see following submit possibilities:
- staging-next -> patch to you (ie. gregkh@xxxxxxx)
- staging-linus -> patch to you (ie. gregkh@xxxxxxx)
- linus tree -> ??
- stable -> patch to stable@xxxxxxxxxx
- final .38 -> ??
2. For the last three targets it is unclear what repo/branch we need to
use
to create our patch upon.
3. For the stable tree it suggest to add Cc: stable@xxxxxxxxxx and add
the upstream (linus tree) commit id. Is this something you will add
when we request it to be applied to those trees or does it require
a separate patch email sent by us?
Hope you can eradicate our confusion.
Could you please confirm my assumptions regarding the questions above:
1. staging-next - used for collecting patches intended for linux-next.
2. staging-linus - used for collecting patches intended for linus tree.
3. patches for stable are based on your staging-linus and we indicate in
the patch that it is intended for stable as well.
4. "final .38" and "linus tree" are one and the same.
5. we should send all patches to you for either staging-next (default) or
staging-linus (indicated in patch).
6. our staging-linus patches are submitted to stable tree by you if we
indicate it in the patch.
Gr. AvS
--
"The most merciful thing in the world, I think, is the inability of the
human
mind to correlate all its contents." - "The Call of Cthulhu"
_______________________________________________
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxx
http://driverdev.linuxdriverproject.org/mailman/listinfo/devel
