To: "Theodore Ts'o" <tytso@mit.edu>
Cc: Sean <seanlkml@sympatico.ca>, Horst von Brand <vonbrand@inf.utfsm.cl>,
       Chris Friesen <cfriesen@nortel.com>, "d.c" <aradorlinux@yahoo.es>,
       cs@tequila.co.jp, galibert@pobox.com, kernel@crazytrain.com,
       linux-kernel@vger.kernel.org
Subject: Re: [BK] upgrade will be needed
References: <seanlkml@sympatico.ca>
	<4912.10.10.10.24.1108675441.squirrel@linux1>
	<200502180142.j1I1gJXC007648@laptop11.inf.utfsm.cl>
	<1451.10.10.10.24.1108713140.squirrel@linux1>
	<20050218162729.GA5839@thunk.org>
From: Miles Bader <miles@lsi.nec.co.jp>
Reply-To: Miles Bader <miles@gnu.org>
System-Type: i686-pc-linux-gnu
Blat: Foop
Date: Mon, 21 Feb 2005 14:43:19 +0900
In-Reply-To: <20050218162729.GA5839@thunk.org> (Theodore Ts'o's message of
 "Fri, 18 Feb 2005 11:27:29 -0500")
Message-ID: <buomzty5uyw.fsf@mctpc71.ucom.lsi.nec.co.jp>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 800
Lines: 16

"Theodore Ts'o" <tytso@mit.edu> writes:
> The "cost" of using BK seems to be primarily more theoretical, and
> ideological, than real.

I've never used BK (not allowed to), but some things I've read about it
sound quite annoying.  For instance:

 * Every source tree contains your entire repository => massive disk usage

 * Must "unlock" files before working on them ("bk edit"); I recall
   doing this with RCS, and it was, well, a real pain.

-Miles
-- 
"Whatever you do will be insignificant, but it is very important that
 you do it."  Mahatma Ghandi
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/