From mboxrd@z Thu Jan 1 00:00:00 1970 From: "David O'Brien" To: Marc Espie Cc: gcc@gcc.gnu.org Subject: Re: repository copy of FreeBSD i386 config file. Date: Wed, 13 Sep 2000 20:23:00 -0000 Message-id: <20000913202334.B93308@dragon.nuxi.com> References: <20000904135248.A46304@dragon.nuxi.com> <200009122102.XAA11873@quatramaran.ens.fr> X-SW-Source: 2000-09/msg00298.html On Tue, Sep 12, 2000 at 11:02:42PM +0200, Marc Espie wrote: > You definitely don't want to move ,v files around on any project > where you wish to keep history and be able to check out old versions > and have them work. True. This is why I was requesting a repository _COPY_. > The only leeway that cvs leaves you, in my experience, is that you > can duplicate a ,v file, to keep a better sense of history of a file Yes. > (this makes it appear as if the file was always there in the old > checkouts). Not quite. It appears on the HEAD only, as the tags (branch point too) are changed. In FreeBSD we prepend "old_" to them. > You still have to make sure a new version of the new file is checked in, > possibly forcibly if you just want to move stuff around. I don't follow this. ``cp old.h,v new.h,v'' will do it. > You'd better have very good reasons for such a hack (such as a 300 > revisions long history), I think you're streaching the amount of history that is important. In what I'm asking, it will be a total pain in the ass to see the changes to freebsd-aout.h after a few changes to it. This because one will have to: cvs up -r freebsd.h cvs up -r freebsd-aout.h diff freebsd.h freebsd-aout.h This is not how CVS was envisioned to be used. > otherwise, the classical > cp old new > cvs rm -f old > cvs add new > cvs commit old new > works just fine. We have found that it doesn't in FreeBSD. -- -- David (obrien@FreeBSD.org)