From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
---|---|
To: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: [COMMITTERS] pgsql: Translation updates |
Date: | 2015-11-10 17:03:41 |
Message-ID: | 20151110170341.GC614468@alvherre.pgsql |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers pgsql-hackers |
Peter Eisentraut wrote:
> Translation updates
>
> Source-Git-URL: git://git.postgresql.org/git/pgtranslation/messages.git
> Source-Git-Hash: cd263526676705b4a8a3a708c9842461c4a2bcc3
Hi Peter,
Would you please document this process? I know it all starts with this
repository,
http://git.postgresql.org/gitweb/?p=pgtranslation/admin.git
and then cp-po-back is used to copy the files from the messages.git repo
to the postgresql.git repo, but it would be better to have more details.
Is there more to it?
(It would also be good to know how to create new branches and how to
destroy one when it goes out of support.)
I would do this by editing this page
https://wiki.postgresql.org/wiki/NLS/admin
and then adding a link to it from
https://wiki.postgresql.org/wiki/Release_process#Before-wrap_tasks
(I decided against doing it myself in case you have different ideas.)
Thanks
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-11-10 21:01:08 | pgsql: Improve our workaround for 'TeX capacity exceeded' in building P |
Previous Message | Robert Haas | 2015-11-09 19:54:42 | pgsql: Stamp 9.5beta2. |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-11-10 17:15:38 | Re: Uh-oh: documentation PDF output no longer builds in HEAD |
Previous Message | Jesper Pedersen | 2015-11-10 17:03:11 | Re: Move PinBuffer and UnpinBuffer to atomics |