public inbox for [email protected]
help / color / mirror / Atom feedFrom: Bruce Momjian <[email protected]>
To: Brendan Jurd <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Posting to hackers and patches lists
Date: Wed, 7 May 2008 10:28:39 -0400 (EDT)
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
Brendan Jurd wrote:
> On Thu, May 8, 2008 at 12:17 AM, Tom Lane <[email protected]> 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
> >
>
> Yes. I can see how posting a URL to a patch would be convenient, but
> having the permanent record of the patch as submitted is important.
>
> What about uploading patches to the wiki? That way we have the
> permanent record (change history), as well as the single authoritative
> location for fetching the latest version.
Right, I was assuming once the patch was uploaded it would be to our
infrastructure and would be permanent.
> > * 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
> >
>
> Well, as long as you send another message to the lists saying "I've
> uploaded a new version of the patch, that URL again is <>". If you
> just silently update the patch without telling anybody you're bound to
> run into problems.
Yep.
--
Bruce Momjian <[email protected]> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
view thread (42+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected]
Subject: Re: Posting to hackers and patches lists
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox