[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <62634bbe-edd6-4973-a96a-df543f39f240@rowland.harvard.edu>
Date: Mon, 11 Nov 2024 19:59:33 -0500
From: Alan Stern <stern@...land.harvard.edu>
To: Szőke Benjamin <egyszeregy@...email.hu>
Cc: paulmck@...nel.org, parri.andrea@...il.com, will@...nel.org,
peterz@...radead.org, boqun.feng@...il.com, npiggin@...il.com,
dhowells@...hat.com, j.alglave@....ac.uk, luc.maranget@...ia.fr,
akiyks@...il.com, dlustig@...dia.com, joel@...lfernandes.org,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
lkmm@...ts.linux.dev, torvalds@...ux-foundation.org
Subject: Re: [PATCH] tools/memory-model: Fix litmus-tests's file names for
case-insensitive filesystem.
On Mon, Nov 11, 2024 at 10:15:30PM +0100, Szőke Benjamin wrote:
> 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'
I support the idea of renaming one of these files. Not to make things
work on case-insensitive filesystems, but simply because having two
files with rather long (and almost nonsensical) names that are identical
aside from one single letter is an excellent way to confuse users.
Come on -- just look at the error report above. Can you tell at a
glance, without going through and carefully comparing the two strings
letter-by-letter, exactly what the difference is? Do you really think
anybody could?
I haven't looked to see if there are any other similar examples in the
litmus-tests directory, but if there are than they should be changed
too.
Alan
Powered by blists - more mailing lists