Tom Lane wrote: > Bruce Momjian <[EMAIL PROTECTED]> 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
This requires the patch submitter to send an email every time they update the URL. The problem with no archive is a problem though. It works for me because I am around to supply versions but I see your point --- perhaps we could make the system have a stable URL but allow for versioning access. Maybe email is a fine interface, of course. -- Bruce Momjian <[EMAIL PROTECTED]> http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
