Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault. - Mailing list pgsql-hackers

From Magnus Hagander
Subject Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.
Date
Msg-id BANLkTinyVvoOc4An9wRf9NUgWtvxYywtkw@mail.gmail.com
Whole thread Raw
In response to Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.  (Michael Meskes <meskes@postgresql.org>)
Responses Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.
Re: Re: [COMMITTERS] pgsql: Fixed string in German translation that causes segfault.
List pgsql-hackers
On Tue, Jun 21, 2011 at 10:20, Michael Meskes <meskes@postgresql.org> wrote:
> On Mon, Jun 20, 2011 at 04:44:20PM -0400, Tom Lane wrote:
>> My recollection is that the current setup was created mainly so that
>> translators wouldn't need to be given commit privileges on the main
>> repo.  Giving them a separate repo to work in might be all right, but
>> of course whoever does the merges would have to be careful to only
>> accept changes made to the .po files and not anything else.
>
> IIRC this is exactly what git submodules are for. We could do a git archive
> only for translations as a submodule for our main git. That way translators
> would only clone the translation git, while we still have the translations in
> the source tree in the main git. At least this is how I think it works.

AFAIK (but I could be wrong), git submodules requires the files to be
in *one* subdirectory. Our .po files are distributed all across the
backend. So we'd have to make (and backpatch) som rather large changes
in how these things are built in order to use that.

--
 Magnus Hagander
 Me: http://www.hagander.net/
 Work: http://www.redpill-linpro.com/


pgsql-hackers by date:

Previous
From: Alexander Korotkov
Date:
Subject: Re: hstore - Implementation and performance issues around its operators
Next
From: Alexey Klyukin
Date:
Subject: Re: proposal: a validator for configuration files