From: Duy Nguyen <pclouds@gmail.com>
Date: Wed, 06 Jan 2016 12:52:21 GMT
Subject: Re: [PATCH 13/16] init: allow alternate backends to be set for new repos
Message-ID: <CACsJy8DQMBfSh1re0jMk1W=d9gYa2=6jqO+Q6bqam5WBY3hfmg@mail.gmail.com>
In-Reply-To: <567AA2DF.1020408@alum.mit.edu>

On Wed, Dec 23, 2015 at 8:34 PM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
> On 12/03/2015 01:35 AM, David Turner wrote:
>> diff --git a/Documentation/git-init.txt b/Documentation/git-init.txt
>> index 8174d27..9ea6753 100644
>> --- a/Documentation/git-init.txt
>> +++ b/Documentation/git-init.txt
>> @@ -12,7 +12,7 @@ SYNOPSIS
>>  'git init' [-q | --quiet] [--bare] [--template=<template_directory>]
>>         [--separate-git-dir <git dir>]
>>         [--shared[=<permissions>]] [directory]
>> -
>> +       [--refs-backend-type=<name>]
>
> ISTM that "backend" (used here in this option name, and in the manpage)
> is not such a meaningful term to users. Could we pick a less obscure
> term? E.g., maybe "--ref-storage=<name>"?

>From an (ex-)translator point of view, storage is also easier to
translate than the technical term "backend". I know we do not
translate option names, but whatever term you use usually show up in
some user-facing messages that need translating. But I do prefer
backend in source code, I think it expresses the idea much better than
storage.
-- 
Duy