linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: BK2CVS problem (fixed)
Date: Tue, 5 Aug 2003 08:41:31 -0700	[thread overview]
Message-ID: <20030805154131.GA20234@work.bitmover.com> (raw)

Several people pointed out problems in the BK2CVS trees.  I spent this
morning checking things over and there were indeed some out of date files.
I've fixed those up and put in place validation tools which should ensure
that this does not happen again.

Here's a validation run:

+ rm -rf /tmp/cmp-tmp
+ mkdir -p /tmp/cmp-tmp/cvs
+ cd /tmp/cmp-tmp/cvs
+ cvs -Q -d /tmp/linux-2.4-cvs checkout -P .
+ cd /tmp/linux-2.4
+ bk export -tplain /tmp/cmp-tmp/bk
+ cd /tmp/cmp-tmp
+ diff -r --exclude=CVS --exclude=BitKeeper --exclude=ChangeSet cvs/linux-2.4 bk
+ test -s DIFFS
+ rm -rf /tmp/cmp-tmp
+ mkdir -p /tmp/cmp-tmp/cvs
+ cd /tmp/cmp-tmp/cvs
+ cvs -Q -d /tmp/linux-2.5-cvs checkout -P .
+ cd /tmp/linux-2.5
+ bk export -tplain /tmp/cmp-tmp/bk
+ cd /tmp/cmp-tmp
+ diff -r --exclude=CVS --exclude=BitKeeper --exclude=ChangeSet cvs/linux-2.5 bk
+ test -s DIFFS
+ cd /tmp/linux-2.4-cvs
+ find linux-2.4 -type f -name '*,v'
+ PID=3553
+ sort
+ xargs sum
+ ssh root@kernel 'cd /home/cvs; find linux-2.4 -type f -name '\''*,v'\'' | xargs sum'
+ sort +2
+ wait 3553
+ diff SUMS SUMS.k
+ test -s DIFFS
+ cd /tmp/linux-2.5-cvs
+ find linux-2.5 -type f -name '*,v'
+ sort
+ PID=3594
+ xargs sum
+ ssh root@kernel 'cd /home/cvs; find linux-2.5 -type f -name '\''*,v'\'' | xargs sum'
+ sort +2
+ wait 3594
+ diff SUMS SUMS.k
+ test -s DIFFS

real    13m8.225s
user    0m23.742s
sys     0m18.830s
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

             reply	other threads:[~2003-08-05 15:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05 15:41 Larry McVoy [this message]
2003-08-05 17:26 ` BK2CVS problem (fixed) Ben Collins

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=20030805154131.GA20234@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;
as well as URLs for NNTP newsgroup(s).