Re: git hooks: too strict check

2022-01-17 Thread Martin Liška
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

Re: git hooks: too strict check

2022-01-14 Thread Eric Gallager via Gcc
On Fri, Jan 14, 2022 at 11:14 AM Michael Matz via Gcc wrote: > > Hello, > > On Fri, 14 Jan 2022, Martin Liška wrote: > > > 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

Re: git hooks: too strict check

2022-01-14 Thread Michael Matz via Gcc
Hello, On Fri, 14 Jan 2022, Martin Liška wrote: > 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: > >

git hooks: too strict check

2022-01-14 Thread Martin Liška
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.*