On Thu, 2011-10-27 at 02:34 +1100, Stephen Rothwell wrote: > Hi Nicholas, > > On Tue, 25 Oct 2011 13:04:10 -0700 "Nicholas A. Bellinger" <nab@xxxxxxxxxxxxxxx> wrote: > > > > On Sun, 2011-10-23 at 23:05 -0700, Nicholas A. Bellinger wrote: > > > > > > The target-pending.git tree is now back on kernel.org, and as before > > > the following branch is used as 'for-next' updates to existing > > > drivers/target/ code: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next > > > > > > I've also added another branch that is being used for new target modules > > > being merged in the next development cycle: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git for-next-merge > > > > > > If you would be so kind, please go ahead and add the second entry as well > > > into your linux-next daily builds. > > > > Just another friendly reminder to please add the for-next-merge branch > > into Next/Trees.. Also if you would, please change the tree names to > > 'target-updates' and 'target-merge' respectively. > > You said above that the for-next-merge branch is for "new target modules > being merged in the next development cycle" which I assumed to mean that > they would be intended for v3.3. As such, I will add that branch after > v3.2-rc1 is released. Let me know if my assumption is incorrect. > Sorry, that is not what I intended to convey. What's currently in for-next-merge it what's slated to go in this merge window.. Apologies for the extra confusion. > I have renamed iscsi-target to target-updates. Thank you. --nab -- To unsubscribe from this list: send the line "unsubscribe linux-next" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
