Re: [PATCH] sv: Updating pg_controldata and pg_ctl.

From: Daniele Varrazzo <daniele(dot)varrazzo(at)gmail(dot)com>
To: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Mats Erik Andersson <bsd(at)gisladisker(dot)se>, pgsql-translators(at)postgresql(dot)org
Subject: Re: [PATCH] sv: Updating pg_controldata and pg_ctl.
Date: 2014-09-24 14:19:47
Message-ID: CA+mi_8bnn9JMrJ_brK7uh4sXvyQuUYjqR1c-dQstgCx-nHoNxg@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-translators

On Wed, Sep 24, 2014 at 2:47 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)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

In response to

Responses

Browse pgsql-translators by date

  From Date Subject
Next Message Alvaro Herrera 2014-09-24 15:00:42 Re: [PATCH] sv: Updating pg_controldata and pg_ctl.
Previous Message Alvaro Herrera 2014-09-24 13:47:45 Re: [PATCH] sv: Updating pg_controldata and pg_ctl.