On Mon, Nov 11, 2024 at 10:39:07PM +0100, Sz"oke Benjamin wrote: [...] > > > > > > There is a technical issue in the Linux kernel source tree's file > > > naming/styles in git clone command on case-insensitive filesystem. > > > > > > > > > warning: the following paths have collided (e.g. case-sensitive paths > > > on a case-insensitive filesystem) and only one from the same > > > colliding group is in the working tree: > > > > > > 'tools/memory-model/litmus-tests/Z6.0+pooncelock+poonceLock+pombonce.litmus' > > > 'tools/memory-model/litmus-tests/Z6.0+pooncelock+pooncelock+pombonce.litmus' > > > > > > > > > As you a maintainer, what is your suggestion to fix it in the source code of > > > the Linux kernel? Please send a real technical suggestion not just how could > > > it be done in an other way (which is out of the scope now). > > > > > > Is my renaming patch correct to solve it? Question is what is the most > > > > No, because once you do a checkout to a commit that previous to your > > changes, things are going to break again. The real "issue" is git use > > case-sensitive file names, so unless you can rewrite the whole history, > > your "solution" goes nowhere. > > > > Regards, > > Boqun > > > > > effective and proper fix/solution which can be commited into the Linux > > > kernel repo to fix it. > > > My renaming solution can not fix the old history line, but after this patch > in latest master branch there are no any issue anymore, in git cloning. This > the bare minimum solution which can fix its "cloning" issue for the future. You asked for a technical issue for doing the renaming, and I gave you one: simply renaming doesn't solve the issue you want to resolve, develop Linux kernel on a case-insensitive filesystem. Do you admit that the original issue won't get fixed with your patch? Then technically, the best way to "work around" it is to use a case-sensitive filesystem, right? Regards, Boqun
