From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | "Ansley, Michael" <Michael(dot)Ansley(at)intec(dot)co(dot)za> |
Cc: | "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgreSQL(dot)org> |
Subject: | Re: [HACKERS] Contributing |
Date: | 1999-07-16 16:35:31 |
Message-ID: | 199907161635.MAA17026@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
[Charset iso-8859-1 unsupported, filtering to ASCII...]
> 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?
Yes, CVS can easily produced the diff for you.
We only allow a few people cvs commmit privs. Others send patches to
the patches list, and we apply them, usually in a few days.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Ross J. Reedstrom | 1999-07-16 16:53:19 | Re: [HACKERS] Contributing |
Previous Message | Ross J. Reedstrom | 1999-07-16 16:32:01 | [leon@udmnet.ru: [GENERAL] Weird behavior of 'default user'] |