From: Larry McVoy <lm@bitmover.com>
To: linux-kernel@vger.kernel.org
Subject: BK problem
Date: Fri, 10 May 2002 10:25:24 -0700 [thread overview]
Message-ID: <200205101725.g4AHPOH05574@work.bitmover.com> (raw)
Hi, we've got a problem in one of Linus' trees and it has started to
propagate around. I need your help to track it down and fix it.
Please run the following script on your Linux BK trees and contact
me if it tells you to do so. You can fix up the tree by doing the
following (warning: takes lots and lots of CPU time so if you don't
need the tree it may well be faster to reclone tomorrow after I finish
fixing the trees on bkbits).
cp SCCS/s.ChangeSet . # save it just in case
bk checksum -vf ChangeSet # takes ~15 minutes on 1Ghz K7
The set of trees which I know are bad on bkbits are:
gkernel/main
linus/linux-2.5
linux-isdn/linux-2.5.export
linuxvm/linus-2.5
ppc/for-linus-ppc64
Here's the script, the usage is
sh SH list of roots of the trees
------------ cut here and store in SH ------------------
#!/bin/sh
test -z "$1" && {
echo "Usage: $0 repo [repo repo...]"
exit 0
}
ID="torvalds@athlon.transmeta.com|ChangeSet|20020205173056|16047|c1d11a41ed024864"
HERE=`pwd`
for tree in "$@"
do cd $HERE
test -f $tree/SCCS/s.ChangeSet || continue
cd $tree
test "`bk identity`" = "$ID" || {
# echo Skipping $tree because ID does not match
continue
}
for i in 20020507175820 20020507172730 20020507171942 \
20020507171816 20020507165445
do bk findkey -t$i ChangeSet
done | bk prs -hnd:KEY: - | bk _keysort > /tmp/k$$
test -s /tmp/k$$ || {
echo $tree is OK, does not have the bad keys
rm /tmp/k$$
continue
}
cmp -s /tmp/k$$ - <<EOF
greg@kroah.com|ChangeSet|20020507171816|03715
greg@kroah.com|ChangeSet|20020507171942|33284
greg@kroah.com|ChangeSet|20020507175820|37065
ink@jurassic.park.msu.ru|ChangeSet|20020507165445|24759
mochel@segfault.osdl.org|ChangeSet|20020507172730|37035
EOF
test $? -eq 0 || {
echo =========================================================
echo $tree needs fixing, contact lm@bitmover.com
echo =========================================================
rm /tmp/k$$
continue
}
echo $tree is fine, it has the fixed keys
rm /tmp/k$$
done
next reply other threads:[~2002-05-10 17:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 17:25 Larry McVoy [this message]
2002-05-10 17:58 ` BK problem Eli Carter
2002-05-10 18:15 ` Larry McVoy
2002-05-10 23:10 ` Larry McVoy
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=200205101725.g4AHPOH05574@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.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