From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Alex Riesen <raa.lkml@gmail.com>
Cc: git@vger.kernel.org, "Shawn O. Pearce" <spearce@spearce.org>
Subject: Re: [PATCH] Fix update-po target to call msgmerge with right parameters
Date: Sun, 22 Jul 2007 12:48:43 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707221246040.14781@racer.site> (raw)
In-Reply-To: <20070722101930.GC3408@steel.home>
Hi,
On Sun, 22 Jul 2007, Alex Riesen wrote:
> Add accidentally forgotten semicolon at the end of msgmerge command line
Good catch!
I did a "make update-po" to test before and after your patch. There seem
to be some changes, but the worst part of it: update-po rewrites almost
the whole file! The .po files contain the line numbers where the message
was found, and they often change.
Oh, well. I'll probably write some alias to see what _actually_
changed (probably just ignoring ^#)...
Ciao,
Dscho
prev parent reply other threads:[~2007-07-22 11:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 10:19 [PATCH] Fix update-po target to call msgmerge with right parameters Alex Riesen
2007-07-22 11:48 ` Johannes Schindelin [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=Pine.LNX.4.64.0707221246040.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=raa.lkml@gmail.com \
--cc=spearce@spearce.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).