I think it depends on the level of changes you intend to implement
(and your 'net access speed). If you just want to tweak some code,
pulling the latest cvs, hacking it up, doing a 'cvs update' and resolve
any conflicts, then doing 'cvs diff' will give you a nice patch to send
in. (Any recomendations on parameters for cvs diff?)
If your planning some major development, where you want to be able to
hack and slash and not worry about losing your own changes, a local CVSup
mirror may be preferable.
Note that if you're behind a slow link, even the first scenario can be slow
(the cvs diff requires 'net access to the repository)
Ross
On Fri, Jul 16, 1999 at 06:10:38PM +0200, Ansley, Michael wrote:
> What is the ideal setup to have when contributing to PG development? I can
> always just download the latest CVS tree, and then presumably run diff when
> I want to send something in.
> However, my understanding is that using CVSup allows me to replicate the cvs
> tree into my own repository, which I then check out/update/commit from/to.
> Then, when I wish to send a patch in, I get cvs to produce a diff on the
> pgsql module. And CVSup allows me to manage changes from the main PG
> repository into my own repository, right?
>
>
> Is this right?
>
> MikeA
>
--
Ross J. Reedstrom, Ph.D., <reedstrm@rice.edu>
NSBRI Research Scientist/Programmer
Computer and Information Technology Institute
Rice University, 6100 S. Main St., Houston, TX 77005