From: "Martin Liška" <mliska@suse.cz>
To: Michael Matz <matz@suse.de>
Cc: GCC Development <gcc@gcc.gnu.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: Re: git hooks: too strict check
Date: Mon, 17 Jan 2022 12:17:44 +0100 [thread overview]
Message-ID: <10395110-ee92-26d2-2b21-feb6a6f3de18@suse.cz> (raw)
In-Reply-To: <alpine.LSU.2.20.2201141607530.4251@wotan.suse.de>
On 1/14/22 17:10, Michael Matz wrote:
> You can't have that, the check is correct. There are filesystems (NTFS
> for instance) that are case-preserving but case-insensitive, on those you
> really can't have two files that differ only in casing. You need to find
> a different solution, either consistently use .cc instead of .C, live with
> the inconsistency or rename the base name of these files.
Thank you for the explanation! I'm going to use a different naming scheme then.
Martin
prev parent reply other threads:[~2022-01-17 11:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:12 Martin Liška
2022-01-14 16:10 ` Michael Matz
2022-01-14 16:27 ` Eric Gallager
2022-01-17 11:17 ` Martin Liška [this message]
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=10395110-ee92-26d2-2b21-feb6a6f3de18@suse.cz \
--to=mliska@suse.cz \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
--cc=matz@suse.de \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).