From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Tanay Abhra <tanayabh@gmail.com>
Cc: git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: [PATCH v5 4/7] rewrite git_config() to use the config-set API
Date: Thu, 31 Jul 2014 13:28:55 +0200 [thread overview]
Message-ID: <vpqegx1ephk.fsf@anie.imag.fr> (raw)
In-Reply-To: <1406799857-28048-5-git-send-email-tanayabh@gmail.com> (Tanay Abhra's message of "Thu, 31 Jul 2014 02:44:14 -0700")
Tanay Abhra <tanayabh@gmail.com> writes:
> + if (!kv_info->linenr)
> + die("unable to parse '%s' from command-line config", entry->key);
> + else
> + die("bad config variable '%s' at file line %d in %s",
Also two missing _("...") here.
Note that there are missing _("...") in config.c before your patch too.
I'll send a patch to fix this regardless of your series.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-07-31 11:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-31 9:44 [PATCH v5 0/7] Rewrite `git_config()` using config-set API Tanay Abhra
2014-07-31 9:44 ` [PATCH v5 1/7] config.c: fix accuracy of line number in errors Tanay Abhra
2014-07-31 9:44 ` [PATCH v5 2/7] add line number and file name info to `config_set` Tanay Abhra
2014-07-31 9:44 ` [PATCH v5 3/7] change `git_config()` return value to void Tanay Abhra
2014-07-31 11:22 ` Matthieu Moy
2014-07-31 11:32 ` Matthieu Moy
2014-07-31 11:52 ` Tanay Abhra
2014-07-31 11:58 ` Matthieu Moy
2014-07-31 9:44 ` [PATCH v5 4/7] rewrite git_config() to use the config-set API Tanay Abhra
2014-07-31 11:28 ` Matthieu Moy [this message]
2014-07-31 9:44 ` [PATCH v5 5/7] add a test for semantic errors in config files Tanay Abhra
2014-07-31 9:44 ` [PATCH 6/7] config: add `git_die_config()` to the config-set API Tanay Abhra
2014-07-31 11:30 ` Matthieu Moy
2014-07-31 9:44 ` [PATCH 7/7] add tests for `git_config_get_string_const()` Tanay Abhra
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=vpqegx1ephk.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=tanayabh@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.
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.