All of lore.kernel.org
 help / color / mirror / Atom feed
From: diekema@bucks.si.com (diekema_jon)
To: cort@ftsoj.fsmlabs.com, linuxppc-embedded@lists.linuxppc.org,
	cort@fsmlabs.com
Subject: Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed
Date: Sat, 6 Jan 2001 11:50:29 -0500 (EST)	[thread overview]
Message-ID: <m14EwY1-001SzWC@bucks> (raw)


It appears that the BitKeeper repository at bk://bitkeeper.fsmlabs.com:5000
has changed.  What happened to the previous BK tree?  Was it replaced with the
2.4.0 baseline?

dell 112} cd ../fsmlabs-linux-2.5
dell 113} bk pull -z9
Nothing to pull.
dell 114} bk parent
Parent repository is bk://hq.fsmlabs.com:5005
dell 115} cd ../fsmlabs-linux-2.5
dell 116} bk parent
Parent repository is bk://hq.fsmlabs.com:5005
dell 117} bk pull -z9
Nothing to pull.
dell 118} cd ../fsmlabs-linux-2.4
dell 119} bk parent
Parent repository is bk://bitkeeper.fsmlabs.com:5000
dell 120} bk pull -z9
You are trying to pull from an unrelated package.  The root keys:
        cort@ftsoj.fsmlabs.com|ChangeSet|20010106071759|19793|5c81b698cda31832
        cort@medea.fsmlabs.com|ChangeSet|19991223032020|43000|42b4afcd8eebec4a
for the ChangeSet file do not match.
Please check the pathnames and try again.

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

             reply	other threads:[~2001-01-06 16:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-06 16:50 diekema_jon [this message]
2001-01-06 17:47 ` Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed Tom Rini
2001-01-06 19:39   ` Wolfgang Denk
2001-01-06 20:11     ` Tom Rini
     [not found]     ` <20010107031448.H13210@hq.fsmlabs.com>
     [not found]       ` <3A58CCC6.75B79975@mvista.com>
2001-01-08 21:22         ` Cort Dougan
2001-01-07 10:13 ` Cort Dougan
2001-01-08 10:03   ` Gabriel Paubert
2001-01-08 21:21     ` Cort Dougan

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=m14EwY1-001SzWC@bucks \
    --to=diekema@bucks.si.com \
    --cc=cort@fsmlabs.com \
    --cc=cort@ftsoj.fsmlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.