From: David Howells <dhowells@redhat.com>
To: "Alexander A. Klimov" <grandmaster@al2klimov.de>
Cc: dhowells@redhat.com, Pablo Neira Ayuso <pablo@netfilter.org>,
Jozsef Kadlecsik <kadlec@netfilter.org>,
Florian Westphal <fw@strlen.de>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Alan Stern <stern@rowland.harvard.edu>,
Andrea Parri <parri.andrea@gmail.com>,
Will Deacon <will@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Boqun Feng <boqun.feng@gmail.com>,
Nicholas Piggin <npiggin@gmail.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
"Paul E. McKenney" <paulmck@kernel.org>,
Akira Yokosawa <akiyks@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
linux-kernel@vger.kernel.org, netfilter-devel@vger.kernel.org,
coreteam@netfilter.org, netdev@vger.kernel.org,
linux-arch@vger.kernel.org
Subject: Re: Good idea to rename files in include/uapi/ ?
Date: Sun, 14 Jun 2020 21:19:25 +0100 [thread overview]
Message-ID: <174102.1592165965@warthog.procyon.org.uk> (raw)
In-Reply-To: <9feded75-4b45-2821-287b-af00ec5f910f@al2klimov.de>
Alexander A. Klimov <grandmaster@al2klimov.de> wrote:
> *Is it a good idea to rename files in include/uapi/ ?*
Very likely not. If programs out there are going to be built on a
case-sensitive filesystem (which happens all the time), they're going to break
if you rename the headers. We're kind of stuck with them.
David
next prev parent reply other threads:[~2020-06-14 20:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-14 19:41 Good idea to rename files in include/uapi/ ? Alexander A. Klimov
2020-06-14 20:19 ` David Howells [this message]
2020-06-14 21:08 ` Jan Engelhardt
2020-06-14 22:01 ` Pablo Neira Ayuso
2020-06-14 23:34 ` Alexander A. Klimov
2020-06-22 11:37 ` Jan Engelhardt
2020-06-22 12:07 ` Pablo Neira Ayuso
2020-06-22 18:06 ` Alexander A. Klimov
2020-06-14 20:34 ` Stefano Brivio
2020-06-14 23:07 ` Alexander A. Klimov
2020-06-15 11:11 ` Geert Uytterhoeven
2020-06-14 22:47 ` Al Viro
2020-06-15 11:12 ` Geert Uytterhoeven
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=174102.1592165965@warthog.procyon.org.uk \
--to=dhowells@redhat.com \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dlustig@nvidia.com \
--cc=fw@strlen.de \
--cc=grandmaster@al2klimov.de \
--cc=j.alglave@ucl.ac.uk \
--cc=kadlec@netfilter.org \
--cc=kuba@kernel.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=npiggin@gmail.com \
--cc=pablo@netfilter.org \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--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 NNTP newsgroup(s).