From: Boqun Feng <boqun.feng@gmail.com>
To: "Sz\"oke Benjamin" <egyszeregy@freemail.hu>
Cc: paulmck@kernel.org, stern@rowland.harvard.edu,
parri.andrea@gmail.com, will@kernel.org, peterz@infradead.org,
npiggin@gmail.com, dhowells@redhat.com, j.alglave@ucl.ac.uk,
luc.maranget@inria.fr, akiyks@gmail.com, dlustig@nvidia.com,
joel@joelfernandes.org, linux-kernel@vger.kernel.org,
linux-arch@vger.kernel.org, lkmm@lists.linux.dev,
torvalds@linux-foundation.org
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem.
Date: Mon, 11 Nov 2024 13:44:21 -0800 [thread overview]
Message-ID: <ZzJ6tWbbdi-zlxS3@tardis.local> (raw)
In-Reply-To: <10ffb1e1-163d-4e30-9be3-0f229f3b7492@freemail.hu>
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
next prev parent reply other threads:[~2024-11-11 21:44 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 16:42 [PATCH] tools/memory-model: Fix litmus-tests's file names for case-insensitive filesystem egyszeregy
2024-11-11 16:54 ` Paul E. McKenney
2024-11-11 18:52 ` Szőke Benjamin
2024-11-11 19:22 ` Paul E. McKenney
2024-11-11 19:56 ` Szőke Benjamin
2024-11-11 20:29 ` Paul E. McKenney
2024-11-11 21:15 ` Szőke Benjamin
2024-11-11 21:23 ` Boqun Feng
2024-11-11 21:39 ` Szőke Benjamin
2024-11-11 21:44 ` Boqun Feng [this message]
2024-11-11 21:52 ` Paul E. McKenney
2024-11-11 22:00 ` Linus Torvalds
2024-11-11 23:21 ` Szőke Benjamin
2024-11-12 1:02 ` Boqun Feng
2024-11-12 10:06 ` Szőke Benjamin
2024-11-12 16:43 ` Paul E. McKenney
2024-11-12 16:56 ` Boqun Feng
2024-11-12 0:59 ` Alan Stern
2024-11-12 4:20 ` Paul E. McKenney
2024-11-12 15:35 ` Alan Stern
2024-11-12 18:26 ` Paul E. McKenney
2024-11-12 20:20 ` Alan Stern
2024-11-12 21:53 ` Paul E. McKenney
2024-12-12 23:09 ` Szőke Benjamin
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=ZzJ6tWbbdi-zlxS3@tardis.local \
--to=boqun.feng@gmail.com \
--cc=akiyks@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=egyszeregy@freemail.hu \
--cc=j.alglave@ucl.ac.uk \
--cc=joel@joelfernandes.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkmm@lists.linux.dev \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.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).