From owner-cvs-gnu Wed Aug 16 19:28:26 1995 Return-Path: cvs-gnu-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id TAA12606 for cvs-gnu-outgoing; Wed, 16 Aug 1995 19:28:26 -0700 Received: from gndrsh.aac.dev.com (gndrsh.aac.dev.com [198.145.92.241]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id TAA12594 ; Wed, 16 Aug 1995 19:28:09 -0700 Received: (from rgrimes@localhost) by gndrsh.aac.dev.com (8.6.11/8.6.9) id TAA21813; Wed, 16 Aug 1995 19:26:27 -0700 From: "Rodney W. Grimes" Message-Id: <199508170226.TAA21813@gndrsh.aac.dev.com> Subject: Re: cvs commit: src/gnu/usr.bin/cvs/cvs import.c To: peter@haywire.dialix.com (Peter Wemm) Date: Wed, 16 Aug 1995 19:26:27 -0700 (PDT) Cc: roberto@blaise.ibp.fr, CVS-commiters@freefall.FreeBSD.org, cvs-gnu@freefall.FreeBSD.org In-Reply-To: from "Peter Wemm" at Aug 17, 95 08:10:09 am X-Mailer: ELM [version 2.4 PL24] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Length: 2138 Sender: cvs-gnu-owner@FreeBSD.org Precedence: bulk > > On Thu, 17 Aug 1995, Ollivier Robert wrote: > > > Now, let me see if I can compile and install this bloody thing on Freefall > > > without too much pain :-). > > > > How about importing CVS 1.5 ? > > > > The remote support is nice to have... > > Umm.. I think this will suprise Rod, who has probably figured out I'm a > "right at the bleeding edge kinga guy", but I think we'd really be > opening up a pandoras box of problems if we enabled remote access... I'd > be having nightmares, Rod would probably be having kittens... :-) I don't need any kittens, and I am sure you could use sound sleep! :-) Now talk about a fast way to talk me right out that idea!! > The main things I'm worried about is the commit process.. In the remote > case, the commit text is prepared on the client, *before* the server even > knows which files are being changed. The server no longer gets to supply > a commit template file, because this is prepared offline now. There's no > longer the visual check of which files you are actually writing the log > message for - you're flying blind unless you've just done a cvs-update. You mean it does not inforce the up to date requirement that local cvs does? Blehhh!!! Un acceptable for our needs. It would be far to easy to smash other commits close togeather time wise. I must be reading this wrong, it just can't be. > I know the NetBSD people use it, and I know cgd had a bumpy ride > getting it running from the early days when remote access was "new". So ... > I don't know.. Is it time to start thinking about this sort of thing a > bit more seriously? It is time to think about it, it is not time to do it. I am glad to know that you are on the bleeding edge with this at your place, that will help collect good data, and help us avoid the pitfalls when we do go forward with it. For now I think we have more important tasks at hand and do not wish to have you loose sleep, or me be chasing after kittens. :-) -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation Company Reliable computers for FreeBSD