Re: [HACKERS] SSL README
Russell Smith wrote: > Alvaro Herrera wrote: > > While you're cleaning up SSL, how about the thread with this email on > > it: > > > > 19212172.post%40talk.nabble.com > > > > > Yeah, I mentioned this to Magnus this morning (my time) and he said > Bruce was compiling a patch in time for the next commit fest. > > I'm not sure where it's all at, but an "official" update would be helpful. Yep, got the patch done, actually; will post it now. -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] SSL README
Alvaro Herrera wrote: > While you're cleaning up SSL, how about the thread with this email on > it: > > 19212172.post%40talk.nabble.com > > Yeah, I mentioned this to Magnus this morning (my time) and he said Bruce was compiling a patch in time for the next commit fest. I'm not sure where it's all at, but an "official" update would be helpful. Russell. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] SSL README
Magnus Hagander wrote: > I notice that there is a src/backend/libpq/README.SSL that contains a > couple of copied emails in it (it even contains our end-of-broadcast > message string!) And it contains a reply to the mail, with quoted stuff! > > In general, this seem to be some hints about how to use things. Things > that if we need them at all, should go in the main manual. It's > certainly not code documentation, so it should not go in a README file > in the sourcetree. > > My suggestion is to just get rid of any enduser docs from that one, and > possibly add stuff to the main manual once we feel it's needed. The part > that documents the SSL "negotiation protocol inside libpq" should stay, > of course. > > Any objections? Agreed, remove it. -- Bruce Momjian <[EMAIL PROTECTED]>http://momjian.us EnterpriseDB http://enterprisedb.com + If your life is a hard drive, Christ can be your backup. + -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
Re: [HACKERS] SSL README
While you're cleaning up SSL, how about the thread with this email on it: 19212172.post%40talk.nabble.com -- Alvaro Herrerahttp://www.CommandPrompt.com/ PostgreSQL Replication, Consulting, Custom Development, 24x7 support -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
[HACKERS] SSL README
I notice that there is a src/backend/libpq/README.SSL that contains a couple of copied emails in it (it even contains our end-of-broadcast message string!) And it contains a reply to the mail, with quoted stuff! In general, this seem to be some hints about how to use things. Things that if we need them at all, should go in the main manual. It's certainly not code documentation, so it should not go in a README file in the sourcetree. My suggestion is to just get rid of any enduser docs from that one, and possibly add stuff to the main manual once we feel it's needed. The part that documents the SSL "negotiation protocol inside libpq" should stay, of course. Any objections? //Magnus -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
