From: Larry McVoy <lm@bitmover.com>
To: Aaron Lehmann <aaronl@vitelus.com>
Cc: Rob Landley <rob@landley.net>, linux-kernel@vger.kernel.org
Subject: Re: BKCVS issue
Date: Mon, 2 Jun 2003 19:28:59 -0700 [thread overview]
Message-ID: <20030603022859.GA26322@work.bitmover.com> (raw)
In-Reply-To: <20030603003739.GG14878@vitelus.com>
On Mon, Jun 02, 2003 at 05:37:39PM -0700, Aaron Lehmann wrote:
> On Mon, Jun 02, 2003 at 07:37:02PM -0400, Rob Landley wrote:
> > On Monday 02 June 2003 17:14, Aaron Lehmann wrote:
> > > For the past few days, it seems like every time something changes in
> > > BK, the bkcvs repository has all of its files touched. At least, all
> > > files in the repository have a P preceding their names on a cvs up.
> > >
> > > It's not intolerable, but I was wondering if anyone's aware of it.
> >
> > CVS thinks of changes as having been applied in a certain order, with each
> > cange applying to the result of previous changes.
>
> I understand that they are built on different models, but I had
> thought the bk->cvs translator was somewhat intelligent. I had never
> seen all the files in the CVS repository touched until a few days ago.
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.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-06-03 2:15 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 [this message]
2003-06-03 6:56 ` Jasper Spaans
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=20030603022859.GA26322@work.bitmover.com \
--to=lm@bitmover.com \
--cc=aaronl@vitelus.com \
--cc=linux-kernel@vger.kernel.org \
--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