From owner-cvs-user Mon Mar 13 23:08:56 1995 Return-Path: cvs-user-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id XAA02524 for cvs-user-outgoing; Mon, 13 Mar 1995 23:08:56 -0800 Received: from ref.tfs.com (ref.tfs.com [140.145.254.251]) by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id XAA02518; Mon, 13 Mar 1995 23:08:54 -0800 Received: (from phk@localhost) by ref.tfs.com (8.6.8/8.6.6) id XAA02802; Mon, 13 Mar 1995 23:07:48 -0800 From: Poul-Henning Kamp Message-Id: <199503140707.XAA02802@ref.tfs.com> Subject: Re: cvs commit: src/release/compat20 libgcc.so.261.0.uu To: bde@zeta.org.au (Bruce Evans) Date: Mon, 13 Mar 1995 23:07:47 -0800 (PST) Cc: bde@zeta.org.au, CVS-commiters@freefall.cdrom.com, cvs-user@freefall.cdrom.com, phk@freefall.cdrom.com, pst@shockwave.com, rgrimes@gndrsh.aac.dev.com In-Reply-To: <199503140655.QAA11402@godzilla.zeta.org.au> from "Bruce Evans" at Mar 14, 95 04:55:56 pm Content-Type: text Content-Length: 709 Sender: cvs-user-owner@freebsd.org Precedence: bulk > >> This only works because libgcc*.c hasn't changed since before FreeBSD-2.0R. > >> If it had changed earlier then we would have already fought this battle. > >checking out to the tag will work. > > For those with cvs'ed sources. nobody else is going to run "make release"... > I'm talking about version control problems. How are you going to maintain > the 2.0 libraries for the 2.1 release? What if there were different > library version numbers for every SNAP? Well, my guess is that this will be an "ad hoc" thing... -- Poul-Henning Kamp -- TRW Financial Systems, Inc. 'All relevant people are pertinent' && 'All rude people are impertinent' => 'no rude people are relevant'