From: lm@bitmover.com (Larry McVoy)
To: andersen@codepoet.org, 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 22:38:53 -0800 [thread overview]
Message-ID: <20050318063853.GA30603@bitmover.com> (raw)
In-Reply-To: <20050318055040.GA16780@codepoet.org>
On Thu, Mar 17, 2005 at 10:50:40PM -0700, Erik Andersen wrote:
> On Thu Mar 17, 2005 at 04:10:53PM -0800, Larry McVoy wrote:
> > 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".
>
> Thanks! Its nice to finally have an open source tool for sucking
> down the latest and greatest directly from bk. Thus far the tool
> is working perfectly at fetching source trees and at updating
> them when new patches are applied.
Great. It _should_ just work, I tested it with patches that included
binaries which changed, it handles that. I suspect we'll find some
case which doesn't work some day (symlinks can't be represented in
a patch for example) but you can always reget things from scratch,
that will work for contents, permissions, symlinks, the works.
> One minor nit. The name for the 'update' tool is a bit too
> generic...
Hey, it's open source, I'm hoping that people will take that code and
evolve it do whatever they need. We're willing to do what we can on
this end if people need protocol changes to support new features,
time permitting. Think of that code as a prototype. It's really
simple, you can hack it trivially.
If you want us to distribute your changes then send a patch, if not
that's cool too. You can take that and evolve it to your heart's
content. If you need a different license to start hacking let me
know what you want, I really don't care, you can have that code
as public domain if you like.
--
---
Larry McVoy lm at bitmover.com http://www.bitkeeper.com
next prev parent reply other threads:[~2005-03-18 6:39 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
2005-03-18 5:50 ` Erik Andersen
2005-03-18 6:38 ` Larry McVoy [this message]
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=20050318063853.GA30603@bitmover.com \
--to=lm@bitmover.com \
--cc=andersen@codepoet.org \
--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