Re: [PATCH 00/65] Mark parseopt strings for translation

From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
Date: May 18, 2012, 04:25 UTC
Message-ID: <CACsJy8DBBxt3Q7bvrC5P-28MXk8KwAno4uDwTQyiRkfictZqdw@mail.gmail.com>
In-Reply-To: <7vlil2v7lx.fsf@alter.siamese.dyndns.org>

On Wed, May 9, 2012 at 1:40 AM, Junio C Hamano <gitster@pobox.com> wrote:

> Both 01/65 (the parse-options implementation) and 02/65 (sample conversion
> of apply.c) made sense, so I'll queue them first.

parseopt-i18n branch [1] has been rebased on master now that the first two patches are merged. I find "git log --patch --color-words=." much easier to review this series (because it just highlights the added parts "N_(" and ")") than line-by-line diff format for email review.

[1] https://github.com/pclouds/git/commits/parseopt-i18n

-- 
Duy

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.