From: "Martin Liška" <mliska@suse.cz>
To: GCC Development <gcc@gcc.gnu.org>,
Joel Brobecker <brobecker@adacore.com>
Subject: git hooks: too strict check
Date: Fri, 14 Jan 2022 15:12:23 +0100 [thread overview]
Message-ID: <f691f009-3c71-e8f5-4f16-8bb45a9b85f4@suse.cz> (raw)
Hello.
I'm working on a testsuite clean-up where some of the files are wrongly named.
More precisely, so files have .cc extension and should use .C. However there's
existing C test-case and it leads to:
marxin@marxinbox:~/Programming/gcc/gcc/testsuite> find . -name test-asm.*
./jit.dg/test-asm.C
./jit.dg/test-asm.c
test-kunlun me/rename-testsuite-files
Enumerating objects: 804, done.
Counting objects: 100% (804/804), done.
Delta compression using up to 16 threads
Compressing objects: 100% (242/242), done.
Writing objects: 100% (564/564), 142.13 KiB | 7.48 MiB/s, done.
Total 564 (delta 424), reused 417 (delta 295), pack-reused 0
remote: Resolving deltas: 100% (424/424), completed with 222 local objects.
remote: *** The following filename collisions have been detected.
remote: *** These collisions happen when the name of two or more files
remote: *** differ in casing only (Eg: "hello.txt" and "Hello.txt").
remote: *** Please re-do your commit, chosing names that do not collide.
remote: ***
remote: *** Commit: 7297e1de9bed96821d2bcfd034bad604ce035afb
remote: *** Subject: Rename tests in jit sub-folder.
remote: ***
remote: *** The matching files are:
remote: ***
remote: *** gcc/testsuite/jit.dg/test-quadratic.C
remote: *** gcc/testsuite/jit.dg/test-quadratic.c
remote: ***
remote: *** gcc/testsuite/jit.dg/test-switch.C
remote: *** gcc/testsuite/jit.dg/test-switch.c
remote: ***
remote: *** gcc/testsuite/jit.dg/test-asm.C
remote: *** gcc/testsuite/jit.dg/test-asm.c
remote: ***
remote: *** gcc/testsuite/jit.dg/test-alignment.C
remote: *** gcc/testsuite/jit.dg/test-alignment.c
Can we please do something about it?
Thanks,
Martin
next reply other threads:[~2022-01-14 14:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 14:12 Martin Liška [this message]
2022-01-14 16:10 ` Michael Matz
2022-01-14 16:27 ` Eric Gallager
2022-01-17 11:17 ` Martin Liška
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=f691f009-3c71-e8f5-4f16-8bb45a9b85f4@suse.cz \
--to=mliska@suse.cz \
--cc=brobecker@adacore.com \
--cc=gcc@gcc.gnu.org \
/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).