repository copy of FreeBSD i386 config file.

[David O'Brien]

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<REVISION_YOU_WANT_TO_COMPARE_WITH> freebsd.h
    cvs up -r<REVISION_YOU_WANT_TO_COMPARE_WITH> 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)