Re: Moving C to its own directory (was Re: ObjC tree inlining)

["David O'Brien" <obrien at FreeBSD dot org>]

On Wed, Nov 21, 2001 at 12:26:17AM +0000, Joseph S. Myers wrote:
> > and w/o repo copies it is an order of
> > magnitude suckier.  FreeBSD has *extensive* experience with repo copies.
> > They work fine.
> 
> You have, for example, always avoided the problem with files both in and
> out of Attic noted at:
> 
> http://mail-index.netbsd.org/tech-misc/2001/08/08/0000.html

Yes.  I have never seen that problem in the FreeBSD CVS repository.
I do not know how those got created in the NetBSD repository.
 
> The essential problem - if you avoid such pitfalls as this - is that it
> creates a *false* history - it claims a file to have been present in some
> given directory with a given name, having had given changes made to it,
> when it wasn't.  

> It also only deals with one very specific problem, that
> of a whole file being moved, 

Yes.  And in this thread that is the specific problem -- wanting to move
a file.

> not of the common case of a large amount of
> text from one file being moved to another.

True, that would not be a repo copy, unless you are spliting foo.c into
foo1.c and foo2.c.  In which case sometimes we would copy foo.c,v to both
foo1.c,v and foo2.c,v.  Then using normal editor and CVS operations cut
foo{1,2}.c down to what they should be; commit them (noting the repo
copied happened) and cvs rm foo.c.

History is kept (and tags are sane if you the script I supplied), and
there is no weirdness in the repo directory.

> You could always adapt CVS
> to allow direct diffing between given revisions of different files without
> needing to copy ,v files or check out those specific revisions.

I'd love to see the patches.  But until they exist, repo copies are what
is available.
 
-- 
-- David  (obrien@FreeBSD.org)