Re: [ANNOUNCE] BK->CVS (real time mirror)

[H. Peter Anvin]

Followup to:  <[e-mail]>
By author:    Larry McVoy <[e-mail]>
In newsgroup: linux.dev.kernel
>
> On Fri, Mar 21, 2003 at 11:40:26AM -0800, H. Peter Anvin wrote:
> > Followup to:  <[e-mail]>
> > By author:    Larry McVoy <[e-mail]>
> > In newsgroup: linux.dev.kernel
> > > 
> > > HPA, should we be mirroring the CVS tarballs to kernel.org?
> > > 
> > 
> > That would be highly useful.  I would also like to see the bk export
> > text file, whatever it's called, mirrored there.
> 
> There is no bk export text file, the output of the export is the CVS
> repository, there isn't anything else.  Everything that we could 
> extract has been extracted and put in CVS.  It's a fairly complete
> and accurate extraction, too.  Far more than the traditional releases
> and pre-releases, I don't know how many of those there have been in
> the 2.5 timeframe but I can't imagine more than a couple hundred;
> there are 8500 commits in the 2.5 CVS tree.  
> 

I was referring to this stuff:

Date: 	Wed, 12 Mar 2003 10:03:04 -0800
X-Hdr-Sender: [e-mail]
From: Larry McVoy <[e-mail]>
Subject: Re: [ANNOUNCE] BK->CVS (real time mirror)
Message-ID: <[e-mail]>
References: <[e-mail]> <[e-mail]>

> I thought that BK has been able to export everything to a text file
> since the first version.

bk export -tpatch -r1.900 > patch.1.900
bk changes -v -r1.900 > comments.1.900

Been there forever.  So has ways to get all the metadata from the command
line without having to reverse engineer the file format.  See

    http://www.bitkeeper.com/manpages/bk-prs-1.html

it's all there.  Always has been.

Wayne wanted me to point that it is easy to write the BK to CVS exporter
completely from the command line, we prototyped it that way, the only
reason we rewrote part of it in C was for performance.  The point being
that you guys could have done this yourself without help from us because
all the metadata is right there.  Ditto for anyone else worried about 
getting their data out of BK now or in the future.  The whole point of
prs is to be able to have a will-always-work way to get at the data or
the metadata, it makes the file format a non-issue.  
-- 
<[e-mail]> at work, <[e-mail]> in private!
"Unix gives you enough rope to shoot yourself in the foot."
Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64