From mboxrd@z Thu Jan 1 00:00:00 1970 Date: Mon, 19 Jan 2004 08:29:54 -0700 From: Tom Rini To: Sven Luther Cc: linuxppc-dev@lists.linuxppc.org, Paul Mackerras Subject: Re: linuxppc trees, what is going on ? Message-ID: <20040119152954.GD13454@stop.crashing.org> References: <20040110084155.GA19817@iliana> <16385.63143.132872.395486@cargo.ozlabs.ibm.com> <20040112073217.GC20938@iliana> <20040113170631.GD10912@stop.crashing.org> <20040113171827.GA13841@iliana> <20040113173513.GE10912@stop.crashing.org> <20040118122134.GA4994@iliana> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <20040118122134.GA4994@iliana> Sender: owner-linuxppc-dev@lists.linuxppc.org List-Id: On Sun, Jan 18, 2004 at 01:21:34PM +0100, Sven Luther wrote: > On Tue, Jan 13, 2004 at 10:35:14AM -0700, Tom Rini wrote: > > > > On Tue, Jan 13, 2004 at 06:18:27PM +0100, Sven Luther wrote: > > > On Tue, Jan 13, 2004 at 10:06:31AM -0700, Tom Rini wrote: > > > > On Mon, Jan 12, 2004 at 08:32:17AM +0100, Sven Luther wrote: > > > > > > > > > Ok, anyway linuxppc_2_4 is supposed to be dead. But my point was, from > > > > > which TAG should i extract kernels from the linuxppc-2.4 to make debian > > > > > packages ? I tried the v2.4.24 tag, which seemed ok, but the version was > > > > > still 2.4.24-rc1. I guess this was a problem due to the haste of the > > > > > 2.4.24 release or something, but it would be nice if it was clear which > > > > > tag we should export. > > > > > > > > There is no tag you can use to do this. Just like how 'v2.4.24' in the > > > > old linuxppc_2_4* trees would get you 2.4.24 w/o any PPC changes, the > > > > same will happen here. > > > > > > This is getting more complicated ... > > > > > > Ok, let's say, tomorrow i need to release a debian 2.4.24 powerpc > > > package, what should i take for this, and which tag/date/whatever should > > > i use. > > > > First, do a bk help changes. I mention this since I believe the > > behavior of -e will change, or has changed. Then do a 'bk changes' such > > that you see all merge changesets. Then just find that one that > > corresponds to when the merge of Marcelo's tree that contained at least > > v2.4.24 came in. If there are changes after v2.4.24, you will have to > > back these out from your patch manually (filterdiff or interdiff can probably > > help here). > > > > Paul, do you want to start adding tags to the linuxppc-2.4 tree? > > I am trully baffled here, i don't know what is going on, but then maybe > it is my little comprehension of how bk works. > > I did pull the linux-2.4 tree, and exported the v2.4.24 tag. I did the > same for the linuxppc-2.4 tree, and diffed the two exported trees. Both > were exactly the same. That is correct. A tag has the same values (set of ChangeSets) regardless of the tree (simpilication). > Could it be possible to add proper tags in the future to the > linuxppc-2.4 tree ? If I do any updates, I'll try and remember to do this. -- Tom Rini http://gate.crashing.org/~trini/ ** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/