| From: | "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za> |
|---|---|
| To: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Contributing |
| Date: | 1999-07-16 16:10:38 |
| Message-ID: | 1BF7C7482189D211B03F00805F8527F70ED04D@S-NATH-EXCH2 |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1999-07-16 16:22:46 | Re: Oversize proc sources (was Re: [BUGS] Backend dies creating plpgsql procedures (with reproducible example!)) |
| Previous Message | Bruce Momjian | 1999-07-16 15:59:50 | Re: [HACKERS] final #include cleanup |