Обсуждение: pgsql: First pass over client applications documentation proofreading.
pgsql: First pass over client applications documentation proofreading.
От
momjian@postgresql.org (Bruce Momjian)
Дата:
Log Message:
-----------
First pass over client applications documentation proofreading.
gabrielle
Modified Files:
--------------
pgsql/doc/src/sgml:
reference.sgml (r1.70 -> r1.71)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/reference.sgml?r1=1.70&r2=1.71)
pgsql/doc/src/sgml/ref:
clusterdb.sgml (r1.25 -> r1.26)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/clusterdb.sgml?r1=1.25&r2=1.26)
createdb.sgml (r1.49 -> r1.50)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/createdb.sgml?r1=1.49&r2=1.50)
createlang.sgml (r1.43 -> r1.44)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/createlang.sgml?r1=1.43&r2=1.44)
createuser.sgml (r1.52 -> r1.53)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/createuser.sgml?r1=1.52&r2=1.53)
dropdb.sgml (r1.35 -> r1.36)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/dropdb.sgml?r1=1.35&r2=1.36)
dropuser.sgml (r1.40 -> r1.41)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/dropuser.sgml?r1=1.40&r2=1.41)
ecpg-ref.sgml (r1.32 -> r1.33)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/ecpg-ref.sgml?r1=1.32&r2=1.33)
pg_dump.sgml (r1.114 -> r1.115)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dump.sgml?r1=1.114&r2=1.115)
pg_dumpall.sgml (r1.79 -> r1.80)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_dumpall.sgml?r1=1.79&r2=1.80)
pg_restore.sgml (r1.82 -> r1.83)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/pg_restore.sgml?r1=1.82&r2=1.83)
psql-ref.sgml (r1.237 -> r1.238)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/psql-ref.sgml?r1=1.237&r2=1.238)
vacuumdb.sgml (r1.50 -> r1.51)
(http://anoncvs.postgresql.org/cvsweb.cgi/pgsql/doc/src/sgml/ref/vacuumdb.sgml?r1=1.50&r2=1.51)
On Feb 18, 2010, at 10:50 PM, momjian@postgresql.org (Bruce Momjian) wrote: > Log Message: > ----------- > First pass over client applications documentation proofreading. > > gabrielle I feel like we ought to be using full names in commit messages. I think I know who is meant, but it might not be so clear to someone looking at this in 5 years. ...Robert
Robert Haas wrote:
> On Feb 18, 2010, at 10:50 PM, momjian@postgresql.org (Bruce Momjian)
> wrote:
> > Log Message:
> > -----------
> > First pass over client applications documentation proofreading.
> >
> > gabrielle
>
> I feel like we ought to be using full names in commit messages. I
> think I know who is meant, but it might not be so clear to someone
> looking at this in 5 years.
Well, for me to use more than that name would require me to go beyond
the submitted email and construct their full name. I actually know the
last name, but because it was not supplied in the email (only
"gabrielle"), I used that. Now, if the author wants to post their full
name on patches, I would certainly use it. The email address is
gorthx@gmail.com.
You will notice the "Proofreader" column on this web site has exactly
the same problem:
http://wiki.postgresql.org/wiki/Documentation_Proofreading
You will also notice that the person has consistently posted using that
name, so it should match pretty easily with an archive search:
http://search.postgresql.org/search?m=1&q=gabrielle&l=&d=&s=
I just did a search and the full name appears very rarely in our
archives, but it does appear.
--
Bruce Momjian <bruce@momjian.us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
On Thu, Feb 18, 2010 at 11:44:06PM -0500, Bruce Momjian wrote: > Robert Haas wrote: > > On Feb 18, 2010, at 10:50 PM, momjian@postgresql.org (Bruce Momjian) > > wrote: > > > Log Message: > > > ----------- > > > First pass over client applications documentation proofreading. > > > > > > gabrielle > > > > I feel like we ought to be using full names in commit messages. I > > think I know who is meant, but it might not be so clear to someone > > looking at this in 5 years. > > Well, for me to use more than that name would require me to go > beyond the submitted email and construct their full name. I > actually know the last name, but because it was not supplied in the > email (only "gabrielle"), I used that. Now, if the author wants to > post their full name on patches, I would certainly use it. The > email address is gorthx@gmail.com. That'd be Gabrielle Roth :) Cheers, David. -- David Fetter <david@fetter.org> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: david.fetter@gmail.com iCal: webcal://www.tripit.com/feed/ical/people/david74/tripit.ics Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate
On Feb 18, 2010, at 10:50 PM, momjian@postgresql.org (Bruce Momjian) wrote: > Log Message: > ----------- > First pass over client applications documentation proofreading. > > gabrielle I feel like we ought to be using full names in commit messages. I think I know who is meant, but it might not be so clear to someone looking at this in 5 years. ...Robert