From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stephen Rothwell Subject: linux-next: tip tree question Date: Mon, 12 Oct 2009 14:56:09 +1100 Message-ID: <20091012145609.c3cc78aa.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg="PGP-SHA1"; boundary="Signature=_Mon__12_Oct_2009_14_56_09_+1100_wOeeOteqUezzpWH1" Return-path: Sender: linux-kernel-owner@vger.kernel.org To: Thomas Gleixner , Ingo Molnar , "H. Peter Anvin" , Peter Zijlstra Cc: linux-next@vger.kernel.org, LKML List-Id: linux-next.vger.kernel.org --Signature=_Mon__12_Oct_2009_14_56_09_+1100_wOeeOteqUezzpWH1 Content-Type: text/plain; charset=US-ASCII Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hi all, I noticed that the auto-latest branch of the tip tree (which is what is included in linux-next) has had the tip out-of-tree branch merged into it. This seems to just introduce lots of commits into linux-next that have nothing to do with the tip tree (some of which contain fixes that are also in Linus' tree) and adds a localversion-tip file. I was wondering if this was done out of necessity or by oversight. I have reverted commit e67d8da85f7a4c2772fe3731de9396b6d01a045e ("Merge branch 'out-of-tree' into auto-latest") from linux-next for today and the x86_64 allmodconfig and powerpc ppc64_defconfig builds still seem OK. --=20 Cheers, Stephen Rothwell sfr@canb.auug.org.au http://www.canb.auug.org.au/~sfr/ --Signature=_Mon__12_Oct_2009_14_56_09_+1100_wOeeOteqUezzpWH1 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (GNU/Linux) iEYEARECAAYFAkrSqNkACgkQjjKRsyhoI8zYswCePQsZgVkcA2A920TiSBPrSrCH 3SAAn22lk4/Yj5DYIVh6j6Om0/CLavzL =nWHp -----END PGP SIGNATURE----- --Signature=_Mon__12_Oct_2009_14_56_09_+1100_wOeeOteqUezzpWH1--