public inbox for [email protected]  

help / color / mirror / Atom feed

From: Tino Wildenhain <[email protected]>
To: Bruce Momjian <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: PostgreSQL-development <[email protected]>
Subject: Re: Posting to hackers and patches lists
Date: Fri, 27 Jun 2008 10:34:22 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>

Bruce Momjian wrote:
> Tom Lane wrote:
...
>>
>> * 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.
> 
What about having tickets? Track for example or something like that
and the submitter feeling an itch to scratch just uploads it to a
ticket. This way you know the reason for a patch and can even have
a little discussion as well as a link to the revision where it
got incorporated. Couldn't be cleaner I think...
The link to the ticket is also rather stable and you can
communicate in mailinglist about it.

Cheers
Tino



Attachments:

  [application/x-pkcs7-signature] smime.p7s (3.2K, 2-smime.p7s)
  download

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