Message-ID: <CAB=NE6XDHL8mexe49TSoug3COh11RAvVY339Ntj0MJdw96wO1w@mail.gmail.com>
Date:	Thu, 8 Dec 2011 13:39:16 -0800
From:	"Luis R. Rodriguez" <mcgrof@...jolero.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	Dani Keerikoolparn <danik@....qualcomm.com>,
	"Hoefel, Guilherme" <hoefel@...lcomm.com>,
	linux-kernel@...r.kernel.org,
	linux-wireless <linux-wireless@...r.kernel.org>
Subject: linux-next base Linus tag

Stephen,

If I know a linux-next tag, say next-20110928, how can I extract the
Linus tag you used to start that set of merges for linux-next for?
That is, I am assuming you base your daily linux-next merges on that
day's latest Linus's rc cycle (not just Linus's master tag of that
day). Is that right? If so how can I get that tag?

For example for next-20110928 I see in Next/quilt-import.log:

diff --git a/Next/quilt-import.log b/Next/quilt-import.log
new file mode 100644
index 0000000..a5c7017
--- /dev/null
+++ b/Next/quilt-import.log
@@ -0,0 +1,12 @@
+Importing hexagon based on v3.1-rc6
+Unchanged quilt series hexagon
+Importing i2c based on 3.1-rc4
+Unchanged quilt series i2c
+Importing jdelvare-hwmon based on 3.1-rc4
+Unchanged quilt series jdelvare-hwmon
+Importing kernel-doc based on 3.1-rc3
+Unchanged quilt series kernel-doc
+Importing rr based on v3.1-rc2-188-g6719db6
+Unchanged quilt series rr
+Importing device-mapper based on v3.1-rc7
+Unchanged quilt series device-mapper

So I see some development trees were based circa v3.1 on different rc
cycles, but its unclear to me which one your linux-next was based on
prior to the merge of git trees / quilt trees.

  Luis
--
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