You'd be ill-adviced to do development against -next, but it does make
sense to check -next before submission.
What to submit depends a bit on who's you'd be submitting to I guess.
Andrew Morton runs a tree itself based on -next and if you'd submit to
him it might make sense to generate the patch against -next.
Generally though, I wouldn't if the difference is just some offsets or
something else small. -next's entire purpose is to do integration work
and while one way of doing that work is ofcourse making everyone _else_
do it, I feel that's not a winning approach in the long run; developers
should concern themselves with their own code, not everyone else's. The
latter is what integrators do.
But surely _checking_ -next makes sense and if there's something
fundamental, you might want to redo the patch on top of it and be
explicit about what you depend on. Or something. Common sense...
Rene.
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@nl.linux.org
Please read the FAQ at http://kernelnewbies.org/FAQ
