Michael J Gruber writes:
> Junio C Hamano venit, vidit, dixit 21.03.2016 21:01:
>
>> If that is the case, perhaps it
>> is also a valid workflow for these collaborating authors of a single
>> document not to update the build product, if they know that nobody
>> cares about how the final output lo
Junio C Hamano venit, vidit, dixit 21.03.2016 21:01:
> Michael J Gruber writes:
>
>> I think this is a general question about how to track build
>> products. The proper place may be in a tree that is referenced
>> from a note or so.
>
>> Maybe I shouldn't consider git.pot a build product - I do
Michael J Gruber writes:
> I think this is a general question about how to track build
> products. The proper place may be in a tree that is referenced
> from a note or so.
> Maybe I shouldn't consider git.pot a build product - I don't know,
> as I honestly don't know why we treat it the way we
2016-03-20 10:45 GMT+01:00 Jiang Xin :
> 2016-03-16 21:33 GMT+08:00 Michael J Gruber :
>> Junio C Hamano venit, vidit, dixit 14.03.2016 18:47:
>>> Junio C Hamano writes:
>>>
But if it makes it easier for translations teams and the i18n
coordinator to work together if I also pulled the gi
2016-03-16 21:33 GMT+08:00 Michael J Gruber :
> Junio C Hamano venit, vidit, dixit 14.03.2016 18:47:
>> Junio C Hamano writes:
>>
>>> But if it makes it easier for translations teams and the i18n
>>> coordinator to work together if I also pulled the git.pot update
>>> myself, I'll do so. I just d
Junio C Hamano venit, vidit, dixit 16.03.2016 17:30:
> Michael J Gruber writes:
>
>> echo '*.po diff=po' >>.gitattributes
>> echo '*.pot diff=po' >>.gitattributes
>> git config diff.po.textconv "msgcat --indent --no-location"
>>
>> With or without the indent, that gives a pretty clean diff. [It's
Duy Nguyen venit, vidit, dixit 16.03.2016 14:40:
> On Wed, Mar 16, 2016 at 8:33 PM, Michael J Gruber
> wrote:
>> In hindsight, what happened must have been like this:
>>
>> "ahead " was marked properly for l10n and translated in the past.
>>
>> 7a76c28 (status: disable translation when --porcelain
Michael J Gruber writes:
> So, in short, I do believe there is a good reason for the "out of sync"
> git.pot. That doesn't make the negative side effect that I describe any
> less true, and I'm looking for ways to ammeliorate that. Something as
> easy as "make check" or "make test-lint".
Yes, I
Junio C Hamano venit, vidit, dixit 14.03.2016 18:47:
> Junio C Hamano writes:
>
>> But if it makes it easier for translations teams and the i18n
>> coordinator to work together if I also pulled the git.pot update
>> myself, I'll do so. I just didn't know (and still don't know) if
>> that makes t
On Wed, Mar 16, 2016 at 8:33 PM, Michael J Gruber
wrote:
> In hindsight, what happened must have been like this:
>
> "ahead " was marked properly for l10n and translated in the past.
>
> 7a76c28 (status: disable translation when --porcelain is used,
> 2014-03-20) introduced those extra parentheses
Michael J Gruber writes:
> echo '*.po diff=po' >>.gitattributes
> echo '*.pot diff=po' >>.gitattributes
> git config diff.po.textconv "msgcat --indent --no-location"
>
> With or without the indent, that gives a pretty clean diff. [It's
> unfortunate that one half of that config is in-tree, one-ha
2016-03-14 23:29 GMT+08:00 Michael J Gruber :
> Hi Junio,
>
> Have you pulled git.pot for 2.8.0 already? [1]
>
> Maybe I'm not up-to-date on the release cycle timing regarding l10n, but
> I was trying to fix a mixed translation/non-translation issue, and it
> turned out the reason is probably that
Max Horn writes:
>> On 11 Mar 2016, at 00:04, Junio C Hamano wrote:
>> ...
>> * "branch --delete" has "branch -d" but "push --delete" does not.
>
> This states a problem, but not whether (and how) it was resolved?
Thanks; how about
* "push" learned that its "--delete" option can be shortened
Junio C Hamano writes:
> But if it makes it easier for translations teams and the i18n
> coordinator to work together if I also pulled the git.pot update
> myself, I'll do so. I just didn't know (and still don't know) if
> that makes things easier for you guys, or if that risks making
> things m
Michael J Gruber writes:
> Have you pulled git.pot for 2.8.0 already? [1]
Thanks for bringing this up.
No, I never pull the "git.pot round N for release" myself, as I am
not working on any translations, and I expect that translation teams
work off of i18n coordinator's tree (i.e. Jiang's tree),
Hi Junio,
Have you pulled git.pot for 2.8.0 already? [1]
Maybe I'm not up-to-date on the release cycle timing regarding l10n, but
I was trying to fix a mixed translation/non-translation issue, and it
turned out the reason is probably that it is not in "git.pot":
"behind " is in git.pot
"ahead "
> On 11 Mar 2016, at 00:04, Junio C Hamano wrote:
>
> A release candidate Git v2.8.0-rc2 is now available for testing
> at the usual places. It is comprised of 459 non-merge commits
> since v2.7.0, contributed by 60 people, 19 of which are new faces.
>
[...]
> Updates since v2.7
> ---
A release candidate Git v2.8.0-rc2 is now available for testing
at the usual places. It is comprised of 459 non-merge commits
since v2.7.0, contributed by 60 people, 19 of which are new faces.
The tarballs are found at:
https://www.kernel.org/pub/software/scm/git/testing/
The following publ
18 matches
Mail list logo
