| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | "Jim C(dot) Nasby" <jim(at)nasby(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Release notes |
| Date: | 2006-09-20 23:27:28 |
| Message-ID: | 200609202327.k8KNRSG27741@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Jim C. Nasby wrote:
> On Wed, Sep 20, 2006 at 05:10:13PM +0100, Simon Riggs wrote:
> > Also, not sure what the thoughts are regarding surnames. I'm referred to
> > as both Simon and Simon Riggs in the release notes. Should we have a
> > policy of first mention uses full name, subsequent mentions just use
> > first name if there is no confusion by doing so?
>
> Hrm, I'd assumed that "well known" community members didn't get Surname
> mentions... maybe we should just stick to "First Last" everywhere..
My system has been to use first names if the person appears at the
bottom of the TODO list, else use full name in all references. We refer
to too many people to use full names only on the first reference.
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-09-20 23:43:22 | pgsql: Add documentation for new in-core advisory lock functions. |
| Previous Message | Matteo Beccati | 2006-09-20 23:25:28 | Re: -HEAD planner issue wrt hash_joins on dbt3 ? |