pg.ddx.io pgsql-docs@postgresql.org mailing list archive
help / color / mirror / Atom feedRE: [HACKERS] Patches
4+ messages / 4 participants
[nested] [flat]
* RE: [HACKERS] Patches
@ 1999-02-01 23:30 Jackson, DeJuan <djackson@cpsgroup.com>
1999-02-01 23:33 ` Re: [HACKERS] Patches Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: Jackson, DeJuan @ 1999-02-01 23:30 UTC (permalink / raw)
To: Bruce Momjian <maillist@candle.pha.pa.us>; tgl@sss.pgh.pa.us; +Cc: darcy@druid.net; pgsql-hackers@postgreSQL.org
So who's maintaining the website?
Drop me a line and let's have a chat about some improvements if you're
interested.
-DEJ
> -----Original Message-----
> > I don't think multiple queues per se are a problem; the
> deficiency I see
> > in our patching procedures is lack of visibility of the status of a
> > proposed patch. If it's not been applied, is it just because no one
> > has gotten to it yet, or was there an objection from
> someone? What's
> > worse is that one of the people with commit access might
> miss or forget
> > about such an objection, and commit a bogus patch anyway
> sometime later.
> > We have enough committers now that I think there's a
> definite risk here.
> >
> > If we wanted to be really organized about this, it'd be cool to have
> > a central database with an item for each proposed patch and links to
> > followup discussions. But I'm not sure it's worth the work it would
> > take to set it up and then maintain the entries. Unless we
> get badly
> > bitten by a mistake that such a database would've
> prevented, it probably
> > won't happen ...
>
> I keep them in my mailbox, delete them if there is objection
> or someone
> else applies it. Eventually, I apply it.
>
> --
> Bruce Momjian | http://www.op.net/~candle
> maillist@candle.pha.pa.us | (610) 853-3000
> + If your life is a hard drive, | 830 Blythe Avenue
> + Christ can be your backup. | Drexel Hill,
> Pennsylvania 19026
>
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: [HACKERS] Patches
1999-02-01 23:30 RE: [HACKERS] Patches Jackson, DeJuan <djackson@cpsgroup.com>
@ 1999-02-01 23:33 ` Bruce Momjian <maillist@candle.pha.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Momjian @ 1999-02-01 23:33 UTC (permalink / raw)
To: djackson@cpsgroup.com; +Cc: tgl@sss.pgh.pa.us; darcy@druid.net; pgsql-hackers@postgreSQL.org; docs@postgreSQL.org
> So who's maintaining the website?
> Drop me a line and let's have a chat about some improvements if you're
> interested.
> -DEJ
We discuss the web site on the docs list, but if it's related to
patches, we can discuss in hackers. I am not the webmaster. You can
reach him at webmaster@postgresql.org.
--
Bruce Momjian | http://www.op.net/~candle
maillist@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 4+ messages in thread
* patches
@ 2002-02-18 21:49 Thomas F. O'Connell <tfo@monsterlabs.com>
2002-02-18 22:14 ` Re: patches Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 1 reply; 4+ messages in thread
From: Thomas F. O'Connell @ 2002-02-18 21:49 UTC (permalink / raw)
To: pgsql-docs
i recently submitted a patch to this mailing list that hasn't been
applied. are docs handled the same way as general postgresql development
in terms of CVS access and whatnot? if so, do i need to clear any sort
of bureaucratic hurdles before i can submit patches?
just curious. figured i'd try to DIY to help the project and save some
time...
-tfo
^ permalink raw reply [nested|flat] 4+ messages in thread
* Re: patches
2002-02-18 21:49 patches Thomas F. O'Connell <tfo@monsterlabs.com>
@ 2002-02-18 22:14 ` Bruce Momjian <pgman@candle.pha.pa.us>
0 siblings, 0 replies; 4+ messages in thread
From: Bruce Momjian @ 2002-02-18 22:14 UTC (permalink / raw)
To: Thomas F. O'Connell <tfo@monsterlabs.com>; +Cc: pgsql-docs
Thomas F. O'Connell wrote:
> i recently submitted a patch to this mailing list that hasn't been
> applied. are docs handled the same way as general postgresql development
> in terms of CVS access and whatnot? if so, do i need to clear any sort
> of bureaucratic hurdles before i can submit patches?
>
> just curious. figured i'd try to DIY to help the project and save some
> time...
I don't see the patch anywhere, neither in my mailbox nor in the 7.3
queue:
http://candle.pha.pa.us/cgi-bin/pgpatches2
Maybe it is stalled in the patches queue. Were you subscribed to
patches list?
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
^ permalink raw reply [nested|flat] 4+ messages in thread
end of thread, other threads:[~2002-02-18 22:14 UTC | newest]
Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1999-02-01 23:30 RE: [HACKERS] Patches Jackson, DeJuan <djackson@cpsgroup.com>
1999-02-01 23:33 ` Bruce Momjian <maillist@candle.pha.pa.us>
2002-02-18 21:49 patches Thomas F. O'Connell <tfo@monsterlabs.com>
2002-02-18 22:14 ` Re: patches Bruce Momjian <pgman@candle.pha.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox