From: Duy Nguyen <pclouds@gmail.com>
To: Justin Lebar <jlebar@google.com>
Cc: Git Mailing List <git@vger.kernel.org>,
Richard Hansen <rhansen@bbn.com>,
Jiang Xin <worldhello.net@gmail.com>
Subject: Re: [PATCH 0/6] Fix misuses of "nor"
Date: Sun, 16 Mar 2014 06:45:30 +0700 [thread overview]
Message-ID: <CACsJy8DrJQvNJUW6Ztjnj71NSPaTz6_A9B=UX3mnhGg7q0a=tQ@mail.gmail.com> (raw)
In-Reply-To: <CAMuNMfri8Sd5pWccnfkE4b1Fdp3i-Cbo6vTk1QVN3SZcOnKvTw@mail.gmail.com>
On Sat, Mar 15, 2014 at 11:56 PM, Justin Lebar <jlebar@google.com> wrote:
> There's a similar incompatibility with the l10n change and "Fix
> misuses of "nor" outside comments": The former references strings
> changed in the latter. Should I merge these, or should I enforce a
> particular ordering between these patches? (Right now the l10n patch
> comes before the string changes in the code, but that's probably wrong
> now that I think about it.)
I think you can drop the l10n patch. After the source code is updated,
new .pot will be generated (probably by Jiang) and .po also
automatically updated. Updated strings in .po are most likely marked
"fuzzy" so translators can double check. So you changes in the source
code will be propagated to .po eventually.
--
Duy
prev parent reply other threads:[~2014-03-15 23:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-15 8:41 [PATCH 0/6] Fix misuses of "nor" Justin Lebar
2014-03-15 8:41 ` [PATCH 1/6] Documentation: " Justin Lebar
2014-03-15 8:41 ` [PATCH 2/6] contrib: " Justin Lebar
2014-03-15 8:41 ` [PATCH 3/6] l10n: " Justin Lebar
2014-03-17 1:45 ` Jiang Xin
2014-03-17 2:43 ` Justin Lebar
2014-03-15 8:42 ` [PATCH 4/6] Fix misuses of "nor" in comments Justin Lebar
2014-03-15 8:42 ` [PATCH 5/6] Fix misuses of "nor" outside comments Justin Lebar
2014-03-15 8:42 ` [PATCH 6/6] Tests: Fix misuses of "nor" Justin Lebar
2014-03-15 8:56 ` [PATCH 0/6] " Duy Nguyen
2014-03-15 16:56 ` Justin Lebar
2014-03-15 23:45 ` Duy Nguyen [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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CACsJy8DrJQvNJUW6Ztjnj71NSPaTz6_A9B=UX3mnhGg7q0a=tQ@mail.gmail.com' \
--to=pclouds@gmail.com \
--cc=git@vger.kernel.org \
--cc=jlebar@google.com \
--cc=rhansen@bbn.com \
--cc=worldhello.net@gmail.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).