Re: CVS should die (was: Possible make_oidjoins_check ...) - Mailing list pgsql-hackers

From Russell Smith
Subject Re: CVS should die (was: Possible make_oidjoins_check ...)
Date
Msg-id 200411050825.09168.mr-russ@pws.com.au
Whole thread Raw
In response to Re: CVS should die (was: Possible make_oidjoins_check ...)  ("Marc G. Fournier" <scrappy@postgresql.org>)
List pgsql-hackers
On Fri, 5 Nov 2004 07:02 am, Marc G. Fournier wrote:
> On Thu, 4 Nov 2004, Tom Lane wrote:
>
> > "Marc G. Fournier" <scrappy@postgresql.org> writes:
> >> why would we lose CVS history?  I can physically move the files in
> >> /cvsroot to accomplish this ... just tell me what needs to move, and to
> >> where ...
> >
> > If you physically move the files, that would retroactively change their
> > placement in back versions, no?  ie, it would appear that all previous
> > releases had had 'em under src/tools as well.
>
> Erk, yes, good point ...
You could always, physically copy the file to the new location. Giving you all the history in the new location
and run CVS delete on the only location.  I can't see how this is too different from the cvs remove/cvs add.
However you get to keep the history as well as keeping the old version.

The second problem still exists where it's in 2 locations in previous releases. unless you cvs remove the new copy from
those branches as well.  As always CVS is a bit messy with these things, but just throwing ideas on the pile that might
work.

Regards

Russell Smith

pgsql-hackers by date:

Previous
From: Joerg Hessdoerfer
Date:
Subject: Re: CVS should die (was: Possible make_oidjoins_check ...)
Next
From: Gaetano Mendola
Date:
Subject: Wrong on-line documentation version