Hi Jon, On Thu, 18 Jun 2009 21:27:11 -0400 Jon Masters <jonathan@xxxxxxxxxxxxxx> wrote: > > I've posted this for merge, but plan to continue developing against the > "master" branch of this tree and then push to "for-linus" before > posting. Perhaps you'd like to add either branch to linux-next. I'll add your for-linus branch to linux-next on Monday (the next tree I will create). What I tell everyone: all patches/commits in the tree/series must have been: posted to a relevant mailing list reviewed unit tested destined for the next merge window (or the current release) *before* they are included. The linux-next tree is for integration testing and to lower the impact of conflicts between subsystems in the next merge window. Basically, this should be just what you would send to Linus (or ask him to fetch). It is allowed to be rebased if you deem it necessary. I'll switch to your master branch if all the above holds for it. Some people have three "public" branches: "bug fixes", "ready for linus" and "development" (called various different things), and I generally stick to the "ready for linus" stuff ... -- Cheers, Stephen Rothwell sfr@xxxxxxxxxxxxxxxx http://www.canb.auug.org.au/~sfr/
Attachment:
pgpAw0aMKftqR.pgp
Description: PGP signature
