From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: "Nguyễn Thái Ngọc Duy" <pclouds@gmail.com>,
"Git List" <git@vger.kernel.org>
Subject: Re: [PATCH] config.txt: stick to CamelCase naming convention
Date: Tue, 10 Mar 2015 16:22:33 -0700 [thread overview]
Message-ID: <xmqqfv9cxwsm.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CAPig+cRkV++D9-yYWOv3FmBtTuWz1_Et23Xk=8cg8=7_E1PZug@mail.gmail.com> (Eric Sunshine's message of "Tue, 10 Mar 2015 16:34:35 -0400")
Eric Sunshine <sunshine@sunshineco.com> writes:
>> @@ -2308,14 +2308,14 @@ sendemail.identity::
>> See linkgit:git-send-email[1] for description. Note that this
>> setting is not subject to the 'identity' mechanism.
>>
>> -sendemail.smtpssl (deprecated)::
>> +sendemail.smtpSSL (deprecated)::
>
> Here, "SSL"...
and not "SMTP". Now what should the rule be when two acronyms sit
next to each other?
I personally feel that we should first fix the obvious
"multipleWords" ones without worrying about abbreviations like ctx
and acronyms and then debate to come up with the rules for the
latter two classes. Most of the ones in the patch look like
"multipleWords" kind that should be uncontroversial.
Duy, thanks for starting this.
next prev parent reply other threads:[~2015-03-10 23:23 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
2015-03-11 12:17 ` Duy Nguyen
2015-03-10 20:34 ` Eric Sunshine
2015-03-10 23:22 ` Junio C Hamano [this message]
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=xmqqfv9cxwsm.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=pclouds@gmail.com \
--cc=sunshine@sunshineco.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.