Re: [PATCH] http: give curl version warnings consistently
From: Junio C Hamano <hidden>
Date: 2018-10-26 04:39:07
Johannes Schindelin [off-list ref] writes:
On Thu, 25 Oct 2018, Junio C Hamano wrote:quoted
When a requested feature cannot be activated because the version of cURL library used to build Git with is too old, most of the codepaths give a warning like "$Feature is not supported with cURL < $Version", marked for l10n. A few of them, however, did not follow that pattern and said things like "$Feature is not activated, your curl version is too old (>= $Version)", and without marking them for l10n. Update these to match the style of the majority of warnings and mark them for l10n. Signed-off-by: Junio C Hamano <redacted> ---I like this patch better than the one I had prepared for v2, so I dropped it again, and "hit the Submit button".
I took your v3 and queue this on top, instead of the previous one
on which this was prepared.
By the way, I wondered if we want to unify them by introducing
static void curl_version_warning(const char *feature, const char *verstring)
{
warning(_("%s is not supported with cURL < %s"),
feature, verstring);
}
so that translators need to deal with a single instance of the
message, but the "feature" part may have to get localized, in which
case we'd end up with sentence lego, which is not a good idea, so I
dropped it.
Thanks.