On Tue, Sep 23, 2014 at 08:34:42AM +1000, Stephen Rothwell wrote: > Hi Josh, > > On Mon, 22 Sep 2014 10:53:04 -0700 Josh Triplett <[email protected]> > wrote: > > > > Can you please add the tiny tree, branch tiny/next of > > https://git.kernel.org/pub/scm/linux/kernel/git/josh/linux.git , to > > linux-next? > > > > I'll be using this tree to upstream various patches for Linux kernel > > tinification. I plan to use topic branches under tiny/* for separate > > topics, typically based on the previous -rc1, merging them into > > tiny/next; when the merge window opens, I'll submit a pull request for > > tiny/next and start merging new tiny/* topic branches into a > > tiny/next-next branch or similar that will become the new tiny/next > > after tiny/next gets merged. > > Added from today. I used git:// instead of https:// for the URL. > > I do not want code for release N in linux-next until after (N-1)-rc1 > has been released.
So, rather than moving tiny/next-next to tiny/next as soon as tiny/next gets merged during the merge window, wait until the end of the merge window (and the release of -rc1) to do so? That makes sense, to avoid causing confusion and unnecessary conflicts during the merge window. The code in tiny/next right now is based on 3.17-rc1, and is intended for 3.18. I'll send a pull request for 3.18 as soon as the 3.18 merge window opens, and any patches I receive after that point will go into tiny/next-next. I'll wait to move tiny/next-next to tiny/next until 3.18-rc1 is released. - Josh Triplett -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
