Messages in this thread | | | Subject | Re: [PATCH updated]: How to be a kernel driver maintainer | From | Arjan van de Ven <> | Date | Mon, 09 Jan 2006 08:46:09 +0100 |
| |
On Sun, 2006-01-08 at 16:45 -0500, Ben Collins wrote: > Here's an updated document. I integrated the suggestions. For Arjan, I > added a new section at the end. Hopefully that addresses the concerns > for cvs-mentality.
it doesn't enough ;(
you still do a major suggestion to keep the code in a repo outside the kernel. For a single driver really that's at best "optional" and shouldn't be the prime recommendation.
"If your driver is affected, you are expected to pick up these changes and merge them with your primary code (e.g. if you have a CVS repo for maintaining your code)."
that sentence is just really the one that I hate. It's bogus. It still calls the private CVS copy "primary". If you do the right thing (and store deltas against mainline and not full code except for scratch stuff) then this is no question of "merging back from mainline" at all.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |