From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Posting to hackers and patches lists |
Date: | 2008-05-07 14:17:53 |
Message-ID: | 6229.1210169873@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches pgsql-www |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> I think it would be helpful for us to provide an infrastructure where
> people who don't run their own servers to store their patches at a
> stable URL where they can keep updating the content. I did that with
> the psql wrap patch and it helped me.
Actually, I find that that is a truly awful habit and I wish that people
would *not* do it that way. There are two reasons why not:
* no permanent archive of the submitted patch
* reviewer won't know if the submitter changes the patch after he
downloads a copy, and in fact nobody will ever know unless the submitter
takes the time to compare the eventual commit to what he thinks the
patch is
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-05-07 14:18:39 | Re: [PATCHES] Testing pg_terminate_backend() |
Previous Message | Bruce Momjian | 2008-05-07 14:08:26 | Posting to hackers and patches lists |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-05-07 14:18:39 | Re: [PATCHES] Testing pg_terminate_backend() |
Previous Message | Bruce Momjian | 2008-05-07 14:08:26 | Posting to hackers and patches lists |
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2008-05-07 14:21:48 | Re: Posting to hackers and patches lists |
Previous Message | Bruce Momjian | 2008-05-07 14:17:03 | Re: [HACKERS] pg_dump additional options for performance |