Subject: Re: CVSup collections for a NetBSD CVS tree
To: NetBSD-current Discussion List <email@example.com>
From: Greg A. Woods <firstname.lastname@example.org>
Date: 05/01/1999 13:01:24
[ On Saturday, May 1, 1999 at 03:06:31 (-0400), Aidan Cully wrote: ]
> Subject: Re: CVSup collections for a NetBSD CVS tree
> > The NetBSD community should not be saying that you can't use CVSup with
> > NetBSD. You might not think you're saying that (as you've tried to
> > claim), but that's most definitely the message that comes across.
> I thought the message that came across was "we don't want to officially
> sanction CVSup as a method for tracking our CVS repository."
It amounts to same thing if you're an outsider looking in, especially
when those outsiders are already well enamoured with CVSup and know the
cost they would pay for going back to a more primitive update system.
> Interesting choice of words.. You say "challenge" where I'd say "burden."
> I don't think we want to port M3 to all of our platforms, and I really
> doubt that anyone apart from us would ever devote any effort into
> maintaining the M3 port after we do, hypothetically, get it working.
In real life things don't always work that way, thankfully. From other
correspondence I've had I would guess that the M3 community would gladly
welcome new ports and given their previous track record in making sure
all ports are maintained with new releases, I don't think we'd end up
with the situation you're hypothesising.
Greg A. Woods
+1 416 218-0098 VE3TCP <email@example.com> <robohack!woods>
Planix, Inc. <firstname.lastname@example.org>; Secrets of the Weird <email@example.com>