| From: | "D'Arcy" "J(dot)M(dot)" Cain <darcy(at)druid(dot)net> |
|---|---|
| To: | pgsql-hackers(at)PostgreSQL(dot)org |
| Subject: | Patches |
| Date: | 1999-01-31 03:42:04 |
| Message-ID: | m106nls-0000bnC@druid.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I sent in a patch for createuser almost a week ago and I was wondering
what the procedure is. I haven't seen the patch applied but I also
haven't seen it rejected. I understand that not every one of my little
gems is going to make it in but I hope there is some sort of closure
method built into the process. In this case I think I have a useful
little addition to createuser but if I am alone, it isn't important
enough to diverge from the standard distribution. I just need to
know one way or the other.
In fact, this is the second time I sent in a similar patch for createuser
and I never heard anything about the first time either and that was before
6.4 was released.
--
D'Arcy J.M. Cain <darcy(at){druid|vex}.net> | Democracy is three wolves
http://www.druid.net/darcy/ | and a sheep voting on
+1 416 424 2871 (DoD#0082) (eNTP) | what's for dinner.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Charles Hornberger | 1999-01-31 05:35:07 | Re: [HACKERS] nested loops in joins, ambiguous rewrite rules |
| Previous Message | D'Arcy J.M. Cain | 1999-01-31 03:27:38 | Re: vacuumdb? |