Re: [PATCH] sv: Updating pg_controldata and pg_ctl.
| От | Daniele Varrazzo |
|---|---|
| Тема | Re: [PATCH] sv: Updating pg_controldata and pg_ctl. |
| Дата | |
| Msg-id | CA+mi_8bnn9JMrJ_brK7uh4sXvyQuUYjqR1c-dQstgCx-nHoNxg@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: [PATCH] sv: Updating pg_controldata and pg_ctl. (Alvaro Herrera <alvherre@2ndquadrant.com>) |
| Ответы |
Re: [PATCH] sv: Updating pg_controldata and
pg_ctl.
|
| Список | pgsql-translators |
On Wed, Sep 24, 2014 at 2:47 PM, Alvaro Herrera <alvherre@2ndquadrant.com> wrote: > Mats Erik Andersson wrote: >> tisdag den 23 september 2014 klockan 21:42 skrev Euler Taveira detta: >> > On 23-09-2014 18:10, Mats Erik Andersson wrote: >> > > I offer a small set for updating two PO-files in Swedish: >> > > >> > Mats, do not send patches (read the steps in [1] -- specially step 4) >> > instead send the whole file. >> >> Why are you then using Git? You should stick with the ticket >> tracker at Pgfoundry for such a workflow. > > Yeah, I mostly agree with Mats here --- that advice was written back > when we were using CVS and as far as I recall we didn't even have > pgfoundry to help us coordinate or the babel site which runs the merge > steps, etc. It should work fine now to ship patches. Would you take in consideration using git as it is intended and have people saying "I've got a few bits of Swedish translated, you can get them from (accessible git url - github or anything else)". A committer could cherry-pick them from the provided source so that even if there were commits in other languages after the contributor forked his repos it would result in no conflict. -- Daniele
В списке pgsql-translators по дате отправления: