public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: lm@bitmover.com (Larry McVoy)
To: Stelian Pop <stelian.pop@fr.alcove.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BKCVS broken ?
Date: Thu, 17 Mar 2005 16:10:53 -0800	[thread overview]
Message-ID: <20050318001053.GA23358@bitmover.com> (raw)
In-Reply-To: <20050317144522.GK22936@hottah.alcove-fr>

I got swamped, I'll look at this after dinner.  But you might take a look
at this: http://www.bitkeeper.com/press/2005-03-17.html which is a link
to a very simple open source BK client.  It doesn't do much except track
the head of the tree but it does that well.  It's slightly better than
that, it puts all the checkin comments in BK/ChangeLog so you don't have
to go over the wire to get those.

It's intended for someone who just wants the latest and greatest snapshot,
knows how to do cp -rp and diff -Nur, it's pretty basic.  It's not a
CVS gateway replacement but it does work for every tree on bkbits.net.
Just to be clear, we are not dropping the CVS gateway, this is "in
addition to" not "instead of".

If this turns out to be popular we can look at making a BitTorrent image
of each tree available so people can get at them without swamping us.

Don't worry about the license, it's a joke.  BSD license OK with everyone?
-- 
---
Larry McVoy                lm at bitmover.com           http://www.bitkeeper.com

  parent reply	other threads:[~2005-03-18  0:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 14:45 BKCVS broken ? Stelian Pop
2005-03-17 15:43 ` Catalin Marinas
2005-03-17 15:44 ` Larry McVoy
2005-03-18  3:07   ` H. Peter Anvin
2005-03-18  0:10 ` Larry McVoy [this message]
2005-03-18  5:50   ` Erik Andersen
2005-03-18  6:38     ` Larry McVoy
2005-03-18  9:00       ` Stelian Pop
2005-03-18 14:13         ` Larry McVoy
2005-03-18 14:21           ` Stelian Pop
2005-03-18 15:08             ` Hong Kong Phoey
2005-03-18 22:09               ` Stelian Pop
2005-03-19 14:52 ` 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=20050318001053.GA23358@bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stelian.pop@fr.alcove.com \
    /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