| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 18 Mar 2013 01:11:02 +0100 From: Samuel Ortiz <sameo@...ux.intel.com> To: Stephen Rothwell <sfr@...b.auug.org.au> Cc: linux-kernel <linux-kernel@...r.kernel.org> Subject: Re: New MFD tree for linux-next On Mon, Mar 18, 2013 at 10:45:20AM +1100, Stephen Rothwell wrote: > On Mon, 18 Mar 2013 00:39:07 +0100 Samuel Ortiz <sameo@...ux.intel.com> wrote: > > > > > I assume that you are still using the for-next branch? > > I will update for-next branch to be in sync with mfd-next until the 3.10 merge > > window closes. After that I'll probably delete the mfd-2.6.git tree. > > I meant "I assume that I should still fetch the for-next branch > of ...sameo/mfd-next.git". If that has changed, please let me know. Sorry for the misunderstanding, I was not clear enough: mfd-next master is replacing mfd-2.6 for-next and mfd-fixes master is replacing mfd-2.6 for-linus. So no need to pull mfd-next for-next. I deleted all branches but master from both mfd-next and mfd-fixes, so things should be clearer now. > > > What branch should I use of that? > > Ah, I didn't see that the remote tree still carries the mfd-2.6 branches, I'll > > remove them. > > Please use master. > > OK. I will do that from tomorrow. Thanks a lot. Cheers, Samuel. -- Intel Open Source Technology Centre http://oss.intel.com/ -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists