linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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	[thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFEEJODLAA.acurtis@onz.com> (raw)
In-Reply-To: <20020903213014.5963.qmail@web40201.mail.yahoo.com>


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

  reply	other threads:[~2002-09-04  5:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-03 21:30 bitkeeper changesets Brian Kuschak
2002-09-04  5:05 ` Allen Curtis [this message]
2002-09-04 14:15   ` Tom Rini
2002-09-04 14:42     ` Allen Curtis
2002-09-04 14:57       ` Tom Rini
2002-09-04 17:26     ` Brian Kuschak
2002-09-04 23:43       ` Tom Rini
  -- strict thread matches above, loose matches on Subject: below --
2002-09-04 16:55 Curtis, Allen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=NCBBIINEHIPFGJPLBEIFEEJODLAA.acurtis@onz.com \
    --to=acurtis@onz.com \
    --cc=bkuschak@yahoo.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).