Re: Refactoring of command.c

Dug the below out of googles cache -- it's what the BSDs do for moving
files in cvs.

What is a repo-copy?
A repo-copy (which is a short form of ``repository copy'') refers to
the direct copying of files within the CVS repository.

Without a repo-copy, if a file needed to be copied or moved to another
place in the repository, the committer would run cvs add to put the
file in its new location, and then cvs rm on the old file if the old
copy was being removed.

The disadvantage of this method is that the history (i.e. the entries
in the CVS logs) of the file would not be copied to the new location.
As the FreeBSD Project considers this history very useful, a
repository copy is often used instead. This is a process where one of
the repository meisters will copy the files directly within the
repository, rather than using the cvs program.

--
Rod Taylor

This message represents the official view of the voices in my head

----- Original Message -----
From: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Rod Taylor" <rbt(at)zort(dot)ca>
Cc: "Bruce Momjian" <pgman(at)candle(dot)pha(dot)pa(dot)us>; "Peter Eisentraut"
<peter_e(at)gmx(dot)net>; "John Gray" <jgray(at)azuli(dot)co(dot)uk>;
<pgsql-hackers(at)postgresql(dot)org>
Sent: Wednesday, February 27, 2002 10:13 AM
Subject: Re: [HACKERS] Refactoring of command.c

> "Rod Taylor" <rbt(at)zort(dot)ca> writes:
> > A simple copy works quite well. Bit of a waste of space but you
> > preserve the history in both locations.
>
> If you do that, the copied file will appear to CVS to be part of
older
> versions, no?
>
> regards, tom lane
>