public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Sun, 14 Dec 2003 15:43:49 -0800	[thread overview]
Message-ID: <20031214234348.GA15850@work.bitmover.com> (raw)
In-Reply-To: <3FDCEF70.5040808@tupshin.com>

On Sun, Dec 14, 2003 at 03:17:04PM -0800, Tupshin Harper wrote:
> I'm sure many people will find this useful. Personally (and this is not 
> intended as any sort of flame bait), I just want a way to get access to 
> all raw bk changesets for a given project. 

I'm sure you do, I've read your postings on various SCM mailing lists.
You'll have to get your test data elsewhere, sorry, we're not in the
business of helping you develop a competing product.  Using BK to do
that is a violation of the free use license and I'm sure you are aware
of that.  

> All existing methods of 
> getting information out of a bk repository either involve running bk 
> yourself, or getting incomplete information. You have argued 
> (succesfully) that the CVS export doesn't lose very much information, 
> but an argument can be made that any information loss is too much. After 
> all, the information I am talking about is simply what was put into the 
> system by the developers in the first place.

Nonsense!  It's the information put in there by BitKeeper.  The BK2CVS 
export is an almost perfect mirror of what you'd get if the developers 
were using CVS or Subversion or whatever.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-12-14 23:43 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44   ` Larry McVoy
2003-12-15  0:25     ` Keith Owens
2003-12-15  3:47       ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43   ` Larry McVoy [this message]
2003-12-15  0:19     ` Tupshin Harper
2003-12-15  3:46       ` Larry McVoy
2003-12-15  6:07         ` Tupshin Harper
2003-12-15 16:02           ` Larry McVoy
2003-12-15 19:52             ` Tupshin Harper
2003-12-15  6:31 ` Martin J. Bligh
2003-12-15 12:11   ` Sergey Vlasov
2003-12-15 13:27     ` Ben Collins
2003-12-15 16:24       ` Sergey Vlasov
2003-12-15 16:32         ` Larry McVoy
2003-12-15 18:31         ` Andrea Arcangeli
2003-12-15 18:58           ` Larry McVoy
2003-12-15 19:40             ` Andrea Arcangeli
2003-12-15 21:44               ` Larry McVoy
2003-12-15 22:02                 ` Andrea Arcangeli
2003-12-15 22:14                   ` Larry McVoy
2003-12-15 22:44                     ` Tupshin Harper
2003-12-15 23:13                       ` Andrea Arcangeli
2003-12-15 22:36                 ` Tupshin Harper
2003-12-15 22:46                   ` Larry McVoy
2003-12-15 23:08                     ` Tupshin Harper
2003-12-17  4:47                       ` Matthew D. Pitts
2003-12-15 15:42   ` Larry McVoy
2003-12-15 15:55     ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46   ` John Bradford
2003-12-24  1:49   ` 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=20031214234348.GA15850@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tupshin@tupshin.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