From: "Torsten Bögershausen" <tboegi@web.de>
To: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] config.txt: stick to CamelCase naming convention
Date: Tue, 10 Mar 2015 15:11:10 +0100 [thread overview]
Message-ID: <54FEFB7E.4020209@web.de> (raw)
In-Reply-To: <1425983981-634-1-git-send-email-pclouds@gmail.com>
On 10.03.15 11:39, Nguyễn Thái Ngọc Duy wrote:
> Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
> ---
> .. while I'm looking at config.txt. I think this is the preferred naming
> convention for config keys.
I think the default is unix-like lowercase,
this is what Git itself produces.
(core.ignorecase, core.filemode, core.precomposeunicode)
next prev parent reply other threads:[~2015-03-10 14:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-10 10:39 [PATCH] config.txt: stick to CamelCase naming convention Nguyễn Thái Ngọc Duy
2015-03-10 14:11 ` Torsten Bögershausen [this message]
2015-03-11 12:17 ` Duy Nguyen
2015-03-10 20:34 ` Eric Sunshine
2015-03-10 23:22 ` Junio C Hamano
2015-03-11 12:20 ` [PATCH v2] *config.txt: stick to camelCase " Nguyễn Thái Ngọc Duy
2015-03-11 20:32 ` Eric Sunshine
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=54FEFB7E.4020209@web.de \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=pclouds@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).