On 3/2/06, Jeff Garzik <[EMAIL PROTECTED]> wrote: > If you want such a separation, you need to separate it yourself. > Otherwise, I have only a single pull target, and thus it can only go > into 2.6.17. > > Example: > > 1) Create branch e1000-fixes with > git checkout -f -b e1000-fixes master > 2) Apply patches 1-11 > 3) Create branch e1000 with > git checkout -f -b e1000 e1000-fixes > 4) Apply patches 12-19. > 5) Note the two branches and their contents -- including "e1000" > dependency on "e1000-fixes" -- in your email. Or, like John Linville > does, send two 'please pull' emails, one for each branch. > > Except for this needed branch split, though, your submission looks OK > from a procedural perspective. I haven't yet reviewed the 19 patches. > > Jeff > > > - > To unsubscribe from this list: send the line "unsubscribe netdev" in > the body of a message to [EMAIL PROTECTED] > More majordomo info at http://vger.kernel.org/majordomo-info.html >
I will split them out for you Jeff. Thanks for the information. -- Cheers, Jeff - To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
