Reminder to patch appliers,
If you apply a patch that was discussed on patches or hackers, please
reply to the email indicating you have applied the patch. I can connect
the commit message to the email discussion but often the patch submitter
does not read committers so it would be good for them
I have created an FTP file containing all ourstanding patches. It is
at:
ftp://candle.pha.pa.us/pub/postgresql/patches.mbox
I will keep this updated so people know their patches are in the queue
and have not been forgotten. I may also use this to ask people for
patch review.
Can
On Wed, Mar 21, 2001 at 10:54:46AM -0500, Bruce Momjian wrote:
Can someone suggest a nice web frontend CGI script to a mbox file, one
that shows sender/subject/date, etc? I don't need to search or modify
the messages, just display them.
Run mhonarc on the mbox. It will create HTML
On Wed, Mar 21, 2001 at 10:54:46AM -0500, Bruce Momjian wrote:
Can someone suggest a nice web frontend CGI script to a mbox file, one
that shows sender/subject/date, etc? I don't need to search or modify
the messages, just display them.
Run mhonarc on the mbox. It will create
On Wed, 21 Mar 2001, Bruce Momjian wrote:
I have created an FTP file containing all ourstanding patches. It is
at:
ftp://candle.pha.pa.us/pub/postgresql/patches.mbox
I will keep this updated so people know their patches are in the queue
and have not been forgotten. I may also use
On Wed, 21 Mar 2001, Bruce Momjian wrote:
I have created an FTP file containing all ourstanding patches. It is
at:
ftp://candle.pha.pa.us/pub/postgresql/patches.mbox
I will keep this updated so people know their patches are in the queue
and have not been forgotten. I may
Bruce Momjian [EMAIL PROTECTED] writes:
I think it is time to start giving people official responsibility for
certain areas of the code.
This strikes me as overly formalistic, and more likely to lead to
arteriosclerosis than any improvement in code quality. Particularly
with a breakdown
The below basically summarizes my opinion quite well ...
On Mon, 19 Mar 2001, Tom Lane wrote:
Bruce Momjian [EMAIL PROTECTED] writes:
I think it is time to start giving people official responsibility for
certain areas of the code.
This strikes me as overly formalistic, and more likely
Bruce Momjian [EMAIL PROTECTED] writes:
I think it is time to start giving people official responsibility for
certain areas of the code.
This strikes me as overly formalistic, and more likely to lead to
arteriosclerosis than any improvement in code quality. Particularly
with a
Bruce Momjian [EMAIL PROTECTED] writes:
I understand the formalistic problem, and maybe I overstated its
formality, but it seems it would be good to maintain a list for two
reasons:
I don't have a problem with keeping an informal list of area experts.
I was just objecting to the notion of
Bruce Momjian [EMAIL PROTECTED] writes:
I understand the formalistic problem, and maybe I overstated its
formality, but it seems it would be good to maintain a list for two
reasons:
In projects like gcc and the GNU binutils, we use a MAINTAINERS file.
Some people have blanket write
Bruce Momjian [EMAIL PROTECTED] writes:
I understand the formalistic problem, and maybe I overstated its
formality, but it seems it would be good to maintain a list for two
reasons:
I don't have a problem with keeping an informal list of area experts.
I was just objecting to the notion
Ian Lance Taylor [EMAIL PROTECTED] writes:
In projects like gcc and the GNU binutils, we use a MAINTAINERS file.
Some people have blanket write privileges. Some people have write
priviliges to certain areas of the code. Anybody else needs a patch
to be approved before they can check it in.
Tom Lane [EMAIL PROTECTED] writes:
Ian Lance Taylor [EMAIL PROTECTED] writes:
In projects like gcc and the GNU binutils, we use a MAINTAINERS file.
Some people have blanket write privileges. Some people have write
priviliges to certain areas of the code. Anybody else needs a patch
to
14 matches
Mail list logo
