From owner-freebsd-java@FreeBSD.ORG Wed Jan 7 13:02:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA09881 for java-outgoing; Wed, 7 Jan 1998 13:02:49 -0800 (PST) (envelope-from owner-freebsd-java@FreeBSD.ORG) Received: from damon.com (root@damon.com [207.170.114.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA09253 for ; Wed, 7 Jan 1998 12:57:17 -0800 (PST) (envelope-from dap@damon.com) Received: (from dap@localhost) by damon.com (8.8.3/8.8.3) id OAA13951; Wed, 7 Jan 1998 14:56:29 -0600 (CST) From: Damon Anton Permezel Message-Id: <199801072056.OAA13951@damon.com> Subject: Re: Motif question To: nate@mt.sri.com (Nate Williams) Date: Wed, 7 Jan 1998 14:56:28 -0600 (CST) Cc: freebsd-java@FreeBSD.ORG, gclarkii@main.brewich.com In-Reply-To: <199801071943.MAA02544@mt.sri.com> from Nate Williams at "Jan 7, 98 12:43:41 pm" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-java@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Nate Williams sez: " > I'm in the process (like in *RIGHT NOW*) setting up a remote CVS tree > that I hope people will consider using for FreeBSD java development. > Access will require that I know you have access to the actual Sun > sources (I have ideas on how to do this), and that you connect to the > site using SSH. I've got a machine setup to do this already, so I don't > forsee any problems, but I am wondering if I actual do this if people > will voluntarily give up 'local access' to their sources and instead try > to move through a centralized tree on a remote site. With a reasonably slow link, I see this as a pain in the ass. However, I think the potential benefits (potentially) far outweigh the above. In suggesting a coordinated approach, I was getting ready to quickly duck if the hairy finger of responsability turned to point in my direction. Getting the patches together to distribute initially was painful enough, and I have been wondering (in my sleep) how I was going to handle the second round of diffs, including others' diffs with mine. Sounds like you have a plan. > > If it does, please reply to the group. Note, unfortunately due to the > nature of the sources, public access won't be made, and the CVS commit > email may or may not be made available. The CVS tree is almost ready to > go, but I have to go through it a bit and sanitize the bits. Not having worked with one of these centralized CVS repositories before, initial concerns include: - what if someone has the file checked out I want? - coordination of effort - resolution of conflicts (please: no #ifdefs)