caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Sven Luther <sven.luther@wanadoo.fr>
To: "Richard W.M. Jones" <rich@merjis.com>
Cc: Sven Luther <sven.luther@wanadoo.fr>, caml-list@inria.fr
Subject: Re: [Caml-list] [OT] Rant about VCS
Date: Sat, 18 Dec 2004 16:39:23 +0100	[thread overview]
Message-ID: <20041218153923.GA3931@pegasos> (raw)
In-Reply-To: <20041218152244.GP27197@annexia.org>

On Sat, Dec 18, 2004 at 03:22:44PM +0000, Richard W.M. Jones wrote:
> On Sat, Dec 18, 2004 at 04:01:51PM +0100, Sven Luther wrote:
> > On Sat, Dec 18, 2004 at 11:24:00AM +0000, Richard Jones wrote:
> > > If you're finding Arch too hard, have a look at Darcs.  This page
> > > describes how to create a repository:
> > > 
> > > http://abridgegame.org/darcs/manual/node4.html
> > 
> > Seems interesting. I wonder if there is a bitkeeper to darcs gateway, that
> > would make it perfect for kernel work.
> 
> There's a Darcs mirror of the Linux kernel, but I don't think it
> includes versions (ie. it's not a true export from BitKeeper).
> 
> http://darcs.net/linux.html
> 
> The problem that Darcs has on repositories of this size is that to do
> its branching and merging magic, it needs to hold the whole codebase
> in memory at once.  With the size of the Linux kernel, this reportedly
> requires about 300MB of real RAM and up to 700MB of virtual memory.
> [Source: http://lwn.net/Articles/110427/]

Main problem seems to be :

 The repository is converted from the bkcvs mirror, and is updated once a day.
 As a result, it doesn't contain any information about file renames.

Seems like a shame to me to go through CVS here, since you loose one of the
important features. And well, what we really need is to get access to any
arbitrary kernel bk trees, not only whichever one was used here.

Friendly,

Sven Luther


  parent reply	other threads:[~2004-12-18 15:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-17 17:07 Alex Baretta
2004-12-17 18:42 ` [Caml-list] " Paul Snively
2004-12-17 19:28   ` Yaron Minsky
2004-12-17 20:13   ` Erik de Castro Lopo
2004-12-17 21:37 ` Sven Luther
2004-12-17 22:27   ` Erik de Castro Lopo
2004-12-18  9:28     ` Sven Luther
2004-12-18  9:49       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 20:03           ` Erik de Castro Lopo
2004-12-18  9:52       ` Erik de Castro Lopo
2004-12-18 14:45         ` Sven Luther
2004-12-18 11:24       ` Richard Jones
2004-12-18 15:01         ` Sven Luther
2004-12-18 15:22           ` Richard W.M. Jones
2004-12-18 15:35             ` Richard W.M. Jones
2004-12-18 15:39             ` Sven Luther [this message]
2004-12-21  9:07     ` [Caml-list] [OT] Rant about VCS: Conclusions Alex Baretta
2004-12-21 22:03       ` Blair Zajac
2004-12-21 22:36         ` Erik de Castro Lopo
2004-12-21 23:19           ` David Brown
2004-12-21 23:47             ` Erik de Castro Lopo
2004-12-18  0:48 ` [Caml-list] [OT] Rant about VCS skaller
2004-12-18 11:25 ` henri dubois-ferriere
2004-12-18 15:03   ` Sven Luther
2004-12-17 18:42 Ennals, Robert
2004-12-17 20:01 ` Alex Baretta
2004-12-17 20:27   ` Paul Snively
2004-12-20  8:27     ` Peter Busser
2004-12-17 20:36   ` Erik de Castro Lopo

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=20041218153923.GA3931@pegasos \
    --to=sven.luther@wanadoo.fr \
    --cc=caml-list@inria.fr \
    --cc=rich@merjis.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;
as well as URLs for NNTP newsgroup(s).