9 jun 2014 kl. 22.02 skrev Ben Reser:
With respect to Subversion for minor releases you can obviously use
the release
candidates. For patch releases you don't get release candidate
tarballs. Once
we've produced a tarball there isn't any opportunity to change
anything.
String changes are n
> -Original Message-
> From: Ben Reser [mailto:b...@reser.org]
> Sent: maandag 9 juni 2014 22:03
> To: Mattias Engdegård
> Cc: dev@subversion.apache.org Development
> Subject: Re: [PATCH] generate subversion.pot in dist.sh
>
> On 6/8/14, 1:59 PM, Mattias Engdegå
On 6/8/14, 1:59 PM, Mattias Engdegård wrote:
> Forgive me for bringing this up again, but we didn't really get anywhere. No
> doubt the thread got lost in the mail traffic somehow.
>
> Are you satisfied with my explanation, or is there still something that makes
> you object to the suggested 2-lin
Forgive me for bringing this up again, but we didn't really get
anywhere. No doubt the thread got lost in the mail traffic somehow.
Are you satisfied with my explanation, or is there still something
that makes you object to the suggested 2-line patch? Having the .pot
file in the source dist
20 maj 2014 kl. 23.11 skrev Ben Reser:
That seems like a really strange workflow to me. If translators are
dependent
on source distributions how are we supposed to have translations
done for
upcoming unreleased changes? I think we can come up with a better
way of doing
this than includin
On 5/20/14, 12:21 PM, Mattias Engdegård wrote:
> The goal is to permit us to use a different translation model, where
> translators aren't working directly in the SVN tree but on .pot files or
> source
> distributions that we give them.
>
> The Translation Project, which I'd like to try first, wo
20 maj 2014 kl. 17.57 skrev Ben Reser:
Why should the pot file be present in the distribution package?
Shouldn't
translators be working against a SVN checkout and not a distribution
package?
The goal is to permit us to use a different translation model, where
translators aren't working d
On 5/6/14, 2:52 PM, Mattias Engdegård wrote:
> Translators will need the subversion.pot file; it should be present in the
> source distribution. Presumably, the right way to ensure that is to have
> dist.sh generate it, similar to the way the configure script is created.
>
> [[[
> Have dist.sh gen
Mattias Engdegård wrote:
> Sorry about the reminder, but are there any objections to the patch or could
> it
> be applied?
It looks good to me, although I haven't tested it. Ben?
- Julian
> 6 maj 2014 kl. 23.52 skrev Mattias Engdegård:
>> Translators will need the subversion.pot file; it shou
Sorry about the reminder, but are there any objections to the patch or
could it be applied?
I have received no comments on it, but perhaps the Apache mail server
gremlins swallowed them.
6 maj 2014 kl. 23.52 skrev Mattias Engdegård:
Translators will need the subversion.pot file; it should be
Translators will need the subversion.pot file; it should be present in
the source distribution. Presumably, the right way to ensure that is
to have dist.sh generate it, similar to the way the configure script
is created.
[[[
Have dist.sh generate subversion.pot for the benefit of translator
11 matches
Mail list logo
