Contributing - Mailing list pgsql-hackers

From Ansley, Michael
Subject Contributing
Date
Msg-id 1BF7C7482189D211B03F00805F8527F70ED04D@S-NATH-EXCH2
Whole thread Raw
Responses Re: [HACKERS] Contributing
Re: [HACKERS] Contributing
Re: [HACKERS] Contributing
List pgsql-hackers
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



pgsql-hackers by date:

Previous
From: wieck@debis.com (Jan Wieck)
Date:
Subject: Re: [HACKERS] Updated TODO list
Next
From: Bruce Momjian
Date:
Subject: Re: Oversize proc sources (was Re: [BUGS] Backend dies creating plpgsql procedures (with reproducible example!))