From: Christian Kujau <evil@g-house.de>
To: linux-kernel <linux-kernel@vger.kernel.org>, support@bitmover.com
Subject: new bk version does not pull?
Date: Sun, 22 Aug 2004 00:05:39 +0200 [thread overview]
Message-ID: <4127C733.90808@g-house.de> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
hi,
a couple of days ago i updated to the latest bk version [1] when i
noticed today, that my repositories are not updated any more:
evil@sheep:/usr/src/linux-2.6-BK$ bk parent
Parent repository is http://linux.bkbits.net/linux-2.5
evil@sheep:/usr/src/linux-2.6-BK$ bk pull
Pull http://linux.bkbits.net/linux-2.5
-> file://usr/src/linux-2.6-BK
Nothing to pull.
evil@sheep:/usr/src/linux-2.6-BK$ head -n1 ChangeSet
torvalds@athlon.transmeta.com|fs/nfs/file.c|20020205173938|09221|5d1b10fca0b197c
torvalds@ppc970.osdl.org|fs/nfs/file.c|20040814105619|14166
- -------------------------------------------^^^^
last update was on 08/14/2004.
(yes, i did "bk -r get")
i guess a "bk clone" will set things right, but i wonder what's up here...
Christian.
[1]
evil@sheep:/usr/src/linux-2.6-BK$ bk version
BitKeeper/Free version is bk-3.2.3 20040814023516 for x86-glibc23-linux
Built by: lm@redhat9.bitmover.com in /build/3.2.x-lm/src
Built on: Sat Aug 14 16:50:49 PDT 2004
Running on: Linux 2.6.8.1
- --
BOFH excuse #250:
Program load too heavy for processor to lift.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBJ8cz+A7rjkF8z0wRAq22AJ9gGIvKt+5HLdCm6RNkMTI6neUqHwCgl9v9
1lET+93huUYHp1hxn6nSFzo=
=XA3B
-----END PGP SIGNATURE-----
next reply other threads:[~2004-08-21 22:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-21 22:05 Christian Kujau [this message]
2004-08-21 22:52 ` new bk version does not pull? Wayne Scott
2004-08-22 2:30 ` Larry McVoy
2004-08-25 12:05 ` Christian Kujau
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=4127C733.90808@g-house.de \
--to=evil@g-house.de \
--cc=linux-kernel@vger.kernel.org \
--cc=support@bitmover.com \
/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.