From: Stefan Beller <sbeller@google.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: Git Mailing list <git@vger.kernel.org>
Subject: Re: is it "core.excludesfile" or "core.excludesFile"?
Date: Thu, 5 Oct 2017 14:32:16 -0700 [thread overview]
Message-ID: <CAGZ79kZof3SWE_Pyb1ADVtkfD2+9ukV+nNBgwxt6xa52Vrmk6A@mail.gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.21.1710051724350.2478@localhost.localdomain>
On Thu, Oct 5, 2017 at 2:25 PM, Robert P. J. Day <rpjday@crashcourse.ca> wrote:
>
> more pedantic nitpickery, but the git source/docs seems to bounce
> all over the place as to which of those forms is the right one.
> opinions?
In the code we use all lowercase to compare (any input is converted to
lowercase);
in the docs we try to come up with a sufficient cameLcase to not
confuse the user.
In tests, I don't know?
next prev parent reply other threads:[~2017-10-05 21:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-05 21:25 is it "core.excludesfile" or "core.excludesFile"? Robert P. J. Day
2017-10-05 21:32 ` Stefan Beller [this message]
2017-10-06 0:47 ` Junio C Hamano
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=CAGZ79kZof3SWE_Pyb1ADVtkfD2+9ukV+nNBgwxt6xa52Vrmk6A@mail.gmail.com \
--to=sbeller@google.com \
--cc=git@vger.kernel.org \
--cc=rpjday@crashcourse.ca \
/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).