From: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>
To: Alexander Kuleshov <kuleshovmail@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] Documentation: config: typo fixed
Date: Thu, 18 Dec 2014 14:40:13 +0100 [thread overview]
Message-ID: <vpqsigd5b5u.fsf@anie.imag.fr> (raw)
In-Reply-To: <1418902079-27794-1-git-send-email-kuleshovmail@gmail.com> (Alexander Kuleshov's message of "Thu, 18 Dec 2014 17:27:59 +0600")
Alexander Kuleshov <kuleshovmail@gmail.com> writes:
> -core.fileMode::
> +core.filemode::
> Tells Git if the executable bit of files in the working tree
> is to be honored.
I do not think that this is a good change: config variable names are
case insensitive, so filemode and fileMode are both correct. The
convention used elsewhere in the documentation is CamelCasing, so the
old version seems better to me.
--
Matthieu Moy
http://www-verimag.imag.fr/~moy/
next prev parent reply other threads:[~2014-12-18 13:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-18 11:27 [PATCH 1/1] Documentation: config: typo fixed Alexander Kuleshov
2014-12-18 11:30 ` Alexander Kuleshov
2014-12-18 13:40 ` Matthieu Moy [this message]
2014-12-18 14:03 ` Alexander Kuleshov
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=vpqsigd5b5u.fsf@anie.imag.fr \
--to=matthieu.moy@grenoble-inp.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=kuleshovmail@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 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 NNTP newsgroup(s).