is it SCCS and the problem is that CSSC doesn't recognise everything that
the latest SCCS does so a patch is needed for CSSC or does it differ
slightly from SCCS?
Larry has mentioned that there were things they changed from the base SCCS
format that they started with, but he indicated that they had fed patches
to SCCS to use the new info.
I'm trying to figure out if the problem is CSSC not being as compatible as
it would like to be or is larry not getting the changes he is proposing
into SCCS, or are there other problems.
On Mon, 3 Mar 2003, nickn wrote:
> Date: Mon, 3 Mar 2003 00:47:28 +0000
> From: nickn <firstname.lastname@example.org>
> To: Jeff Garzik <email@example.com>
> Cc: H. Peter Anvin <firstname.lastname@example.org>, email@example.com
> Subject: Re: BitBucket: GPL-ed *notrademarkhere* clone
> On Sun, Mar 02, 2003 at 12:12:58PM -0500, Jeff Garzik wrote:
> > My counter-question is, why not improve an _existing_ open source SCM to
> > read and write BitKeeper files? Why do we need yet another brand new
> > project?
> Or improve BK to export and import on demand of an existing open source SCM.
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to firstname.lastname@example.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/