From: Ben Collins <bcollins@debian.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: andrea@e-mind.com, kernel list <linux-kernel@vger.kernel.org>
Subject: Re: BitBucket: GPL-ed BitKeeper clone
Date: Sun, 2 Mar 2003 19:53:59 -0500 [thread overview]
Message-ID: <20030303005359.GG458@phunnypharm.org> (raw)
In-Reply-To: <20030302235318.GB319@elf.ucw.cz>
On Mon, Mar 03, 2003 at 12:53:18AM +0100, Pavel Machek wrote:
> Hi!
>
> > > > I've created little project for read-only (for now ;-) bitkeeper
> > > > clone. It is available at www.sf.net/projects/bitbucket (no tar balls,
> > > > just get it fresh from CVS).
> > >
> > > In case it may be of some help, here's a script that is the result of my
> > > own reverse engineering of the bitkeeper SCCS files. It can output a
> > > diff, almost exactly the same as BitKeeper's gnupatch output from a
> > > BitKeeper repo.
> >
> > Might aswell supply my hacked sccsdiff script aswell.
>
> There's a problem with this: it changes CSSC, and its GNU (read: needs
> copyright assignment to apply changes). I can't really push your
> changes to CSSC :-(. [What I can do is add .diff file into
> bitbucket...]
I'm putting my changes to CSSC into the public domain. The FSF can do
whatever it wants.
--
Debian - http://www.debian.org/
Linux 1394 - http://www.linux1394.org/
Subversion - http://subversion.tigris.org/
Deqo - http://www.deqo.com/
prev parent reply other threads:[~2003-03-03 0:45 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 20:02 BitBucket: GPL-ed BitKeeper clone Pavel Machek
2003-03-01 15:28 ` Larry McVoy
2003-03-01 16:02 ` Ben Collins
2003-03-01 16:11 ` Larry McVoy
2003-03-01 17:30 ` Alan Cox
2003-03-01 16:40 ` John Bradford
2003-03-01 16:42 ` Ben Collins
2003-03-02 23:40 ` Pavel Machek
2003-03-01 17:01 ` Aaron Lehmann
2003-03-01 17:19 ` Bernd Eckenfels
2003-03-01 18:05 ` BitBucket: GPL-ed KitBeeper clone Pavel Janík
2003-03-01 18:39 ` Christoph Hellwig
2003-03-01 22:43 ` Pavel Janík
2003-03-02 9:11 ` Christoph Hellwig
2003-03-02 9:30 ` John Bradford
2003-03-02 9:32 ` Christoph Hellwig
2003-03-03 12:39 ` Pavel Machek
2003-03-03 14:12 ` Alan Cox
2003-03-03 13:57 ` John Bradford
2003-03-03 14:22 ` Richard B. Johnson
2003-03-03 15:08 ` John Bradford
2003-03-03 17:50 ` David Lang
2003-03-03 19:37 ` Pavel Machek
2003-03-03 19:49 ` John Bradford
2003-03-03 14:22 ` Charles Cazabon
2003-03-02 9:57 ` Pavel Janík
2003-03-03 8:05 ` Helge Hafting
2003-03-03 8:28 ` Bernd Eckenfels
2003-03-01 20:58 ` Paul Fulghum
2003-03-02 4:52 ` Mike Galbraith
2003-03-03 0:02 ` Pavel Machek
2003-03-02 5:04 ` BitBucket: GPL-ed BitKeeper clone Ben Collins
2003-03-02 5:10 ` Ben Collins
2003-03-02 23:53 ` Pavel Machek
2003-03-03 0:53 ` Ben Collins [this message]
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=20030303005359.GG458@phunnypharm.org \
--to=bcollins@debian.org \
--cc=andrea@e-mind.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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