From: Jasper Spaans <jasper@vs19.net>
To: Larry McVoy <lm@work.bitmover.com>,
Aaron Lehmann <aaronl@vitelus.com>, Rob Landley <rob@landley.net>,
linux-kernel@vger.kernel.org
Subject: Re: BKCVS issue
Date: Tue, 3 Jun 2003 08:56:39 +0200 [thread overview]
Message-ID: <20030603065639.GA5093@spaans.vs19.net> (raw)
In-Reply-To: <20030603022859.GA26322@work.bitmover.com>
On Mon, Jun 02, 2003 at 07:28:59PM -0700, Larry McVoy wrote:
> It is intelligent but it is busted, believe me, I know. The conversion
> happens on my desktop and it thrashes the hell out of the disk when
> CVS tags.
>
> We're swamped working on a BK release, that's our first priority. As soon
> as I get a breather I'll get back to the bk2cvs convertoer.
Just a small pointer which might help, when looking at the cvslog of any
file in the bkcvs repository:
RCS file: /home/cvs/linux-2.5/Makefile,v
Working file: Makefile
head: 1.376
branch:
locks: strict
access list:
symbolic names:
found: 1.376
not: 1.376
command: 1.376
v2_5_70: 1.356
[...]
So it seems something is b0rken wrt tagging...
Otherwise it's a mighty fine service, thanks a lot for providing it.
Bye,
--
Jasper Spaans
http://jsp.vs19.net/contact/
``Got no clue? Too bad for you.''
next prev parent reply other threads:[~2003-06-03 6:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-02 21:14 BKCVS issue Aaron Lehmann
2003-06-02 23:37 ` Rob Landley
2003-06-02 23:39 ` Ben Collins
2003-06-03 0:50 ` Rob Landley
2003-06-03 0:03 ` Ben Collins
2003-06-03 0:37 ` Aaron Lehmann
2003-06-03 2:28 ` Larry McVoy
2003-06-03 6:56 ` Jasper Spaans [this message]
2003-06-05 20:54 ` 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=20030603065639.GA5093@spaans.vs19.net \
--to=jasper@vs19.net \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@work.bitmover.com \
--cc=rob@landley.net \
/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