Date: Fri, 14 Nov 2003 07:00:47 -0800
From: Larry McVoy <lm@bitmover.com>
To: Andrew Walrond <andrew@walrond.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: kernel.bkbits.net off the air
Message-ID: <20031114150047.GC30711@work.bitmover.com>
Mail-Followup-To: Larry McVoy <lm@work.bitmover.com>,
	Andrew Walrond <andrew@walrond.org>, linux-kernel@vger.kernel.org
References: <fa.eto0cvm.1v20528@ifi.uio.no> <200311131917.11773.andrew@walrond.org> <20031113192839.GA13330@work.bitmover.com> <200311132057.53026.andrew@walrond.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200311132057.53026.andrew@walrond.org>
User-Agent: Mutt/1.4i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1101
Lines: 22

On Thu, Nov 13, 2003 at 08:57:53PM +0000, Andrew Walrond wrote:
> The point. You got one major o/s project hosted on bk when you ought to have 
> them all. Loads more developers using bk at home means loads more demanding 
> it at work.
> 
> And all it would take is a lobotomised, redistributable, license free client 
> so anyone can pull o/s software from bk repos.

One of us is not getting it, maybe it's me.  To build something like
you describe is pretty easy IF AND ONLY IF all you are asking for is an
update mechanism.  As soon as you want revision history, diffs, rollbacks,
modifiable files, etc., you have to go to real BK.  Is that OK?  All you
want is a "keep me up to date" mechanism?  No diffs, no history, it's a
replacement for tarballs and patches?
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm
-
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/