public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Jonathan A. George" <JGeorge@greshamstorage.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel SCM: When does CVS fall down where it REALLY matters?
Date: Mon, 11 Mar 2002 11:53:38 -0600	[thread overview]
Message-ID: <3C8CEF22.1050602@greshamstorage.com> (raw)
In-Reply-To: <Pine.LNX.4.33L2.0203110911530.3326-100000@dragon.pdx.osdl.net>

On Mon, 11 Mar 2002, Larry McVoy wrote:

>Arch has a concept of an "inode" quite similar to BitKeeper, in fact
>one wonders where the idea came from :-)
>
Oh please.  I've used the concept of an "inode" for years when modeling 
the information related to filesystem attributes simply because that is 
what the filesystem itself uses, and when modeling something in a 
filesystem the concept is self evident.  I'm certain that every deep 
version control system has a similar model (i.e. Clearcase which 
explicitly is a filesystem)...  It's not as if people are unaware of the 
deficiencies of CVS and other free software version control systems, 
they simply haven't yet invested the time to polish them because the 
development cost failed the cost benefit analysis test for them.

I must give you credit for stirring things up and showing how great the 
benefits are of a polished SCM system to the free software community. 
 However, between my computer science background and use of various 
commercial SCM systems I see great polish and followthrough in 
bitkeeper, but not much true originality.  In other words your dig at 
Tom was really out of line.

--Jonathan--


  parent reply	other threads:[~2002-03-11 17:54 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-07 23:51 Kernel SCM: When does CVS fall down where it REALLY matters? Jonathan A. George
2002-03-07 23:59 ` Rik van Riel
2002-03-08  0:03   ` Cort Dougan
2002-03-09 11:17     ` Roman Zippel
2002-03-09 16:45       ` Kurt Roeckx
2002-03-08  0:26   ` Andrew Morton
2002-03-08  0:36     ` Rik van Riel
2002-03-08  1:48     ` Neil Brown
2002-03-10 20:27       ` Pavel Machek
2002-03-11 21:11         ` Rik van Riel
2002-03-12 16:31           ` Pavel Machek
2002-03-08  7:37     ` Alex Riesen
2002-03-08  0:29   ` Jonathan A. George
2002-03-08  0:43     ` Rik van Riel
2002-03-08  9:32       ` Pau Aliagas
2002-03-08 16:37         ` Rik van Riel
2002-03-08 20:15           ` Pau Aliagas
2002-03-08 20:22             ` Rik van Riel
2002-03-08 20:28               ` Pau Aliagas
2002-03-08  0:38   ` Erik Andersen
2002-03-08  9:38     ` Pau Aliagas
2002-03-09  1:52     ` Val Henson
2002-03-09  2:00       ` Mike Fedyk
2002-03-09  2:25       ` Dave Jones
2002-03-08  1:19   ` Dave Jones
2002-03-08 20:27     ` Jonathan A. George
2002-03-08 21:59       ` Eli
2002-03-08  3:15   ` H. Peter Anvin
2002-03-08  9:39     ` Pau Aliagas
2002-03-11 17:05   ` Larry McVoy
2002-03-11 17:12     ` Randy.Dunlap
2002-03-11 17:25       ` Larry McVoy
2002-03-11 17:53       ` Jonathan A. George [this message]
2002-03-11 18:03         ` Larry McVoy
2002-03-11 20:36     ` Rik van Riel
2002-03-11 21:01       ` Larry McVoy
2002-03-11 21:28         ` Rik van Riel
2002-03-10 19:28 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2002-03-09 22:22 Tom Lord
2002-03-11 17:10 ` Larry McVoy
2002-03-12  6:09   ` Tom Lord

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=3C8CEF22.1050602@greshamstorage.com \
    --to=jgeorge@greshamstorage.com \
    --cc=linux-kernel@vger.kernel.org \
    /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