From mboxrd@z Thu Jan  1 00:00:00 1970
Reply-To: <acurtis@onz.com>
From: "Allen Curtis" <acurtis@onz.com>
To: "Brian Kuschak" <bkuschak@yahoo.com>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: RE: bitkeeper changesets
Date: Tue, 3 Sep 2002 22:05:30 -0700
Message-ID: <NCBBIINEHIPFGJPLBEIFEEJODLAA.acurtis@onz.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
In-Reply-To: <20020903213014.5963.qmail@web40201.mail.yahoo.com>
Sender: owner-linuxppc-embedded@lists.linuxppc.org
List-Id: <linuxppc-embedded@lists.linuxppc.org>


> I'm using the BK changeset versions for tracking when
> I export specific BK trees into my local
> source-control system.  The last one I imported was
> 2.4.19-final (changeset 1.1114 on 08-02-2002).  Today
> I did a 'bk pull', and noticed that that changeset
> revision no longer exists in BK!  And it seems the one
> I exported previously is now named 1.1091.1.23.
>
> Also, it seems like older versions (earlier than
> 29-May-2002) are no longer available in BK.
>
> Am I missing something here, or did the version
> numbers really change?  And why?  Should I be using a
> different BK server?

I see the same thing. It looks like the tag changed to just v2.4.19. The BK
revisions totally changed!


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/