From: Junio C Hamano <gitster@pobox.com>
To: Paul Mackerras <paulus@ozlabs.org>
Cc: David Aguilar <davvid@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] gitk: remove translated message from comments
Date: Wed, 18 Jan 2017 10:27:34 -0800 [thread overview]
Message-ID: <xmqqd1fkb4vd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170118101515.GA12161@fergus.ozlabs.ibm.com> (Paul Mackerras's message of "Wed, 18 Jan 2017 21:15:15 +1100")
Paul Mackerras <paulus@ozlabs.org> writes:
> On Tue, Jan 17, 2017 at 07:52:45PM -0800, David Aguilar wrote:
>> "make update-po" fails because a previously untranslated string
>> has now been translated:
>>
>> Updating po/sv.po
>> po/sv.po:1388: duplicate message definition...
>> po/sv.po:380: ...this is the location of the first definition
>>
>> Remove the duplicate message definition.
>>
>> Reported-by: Junio C Hamano <gitster@pobox.com>
>> Signed-off-by: David Aguilar <davvid@gmail.com>
>
> Thanks, applied.
>
> Junio, please do a pull from my repository to get this fix.
> The new head is 7f03c6e32891.
Thanks.
prev parent reply other threads:[~2017-01-18 18:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-01 17:03 gitk: "lime" color incompatible with older Tk versions Andrew Janke
2016-05-02 16:20 ` Stefan Beller
2017-01-13 11:20 ` David Aguilar
2017-01-14 8:48 ` gitk pull request // was: " David Aguilar
2017-01-15 2:35 ` Junio C Hamano
2017-01-16 3:17 ` Paul Mackerras
2017-01-16 7:48 ` Junio C Hamano
2017-01-17 18:34 ` Junio C Hamano
2017-01-18 3:52 ` [PATCH] gitk: remove translated message from comments David Aguilar
2017-01-18 10:15 ` Paul Mackerras
2017-01-18 18:27 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqd1fkb4vd.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=paulus@ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.