From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
David Howells <dhowells@redhat.com>,
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
Subject: Re: Good idea to rename files in include/uapi/ ?
Date: Mon, 22 Jun 2020 14:07:07 +0200 [thread overview]
Message-ID: <20200622120707.GA17620@salvia> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2006221336180.26495@n3.vanv.qr>
On Mon, Jun 22, 2020 at 01:37:09PM +0200, Jan Engelhardt wrote:
>
> On Monday 2020-06-15 01:34, Alexander A. Klimov wrote:
> >>
> >> A header file rename is no problem. We even have dummy headers
> > Hmm.. if I understand all of you correctly, David, Stefano, Pablo and Al say
> > like no, not a good idea, but only you, Jan, say like should be no problem.
> >
> > Jan, do you have anything like commit messages in mainline or public emails
> > from maintainers confirming your opinion?
>
> I had already given the commit with the (email) message:
>
> >> Just look at xt_MARK.h, all it does is include xt_mark.h. Cf.
> >> 28b949885f80efb87d7cebdcf879c99db12c37bd .
Why rename this in 2020 ?
WARNING: multiple messages have this Message-ID (diff)
From: Pablo Neira Ayuso <pablo@netfilter.org>
To: Jan Engelhardt <jengelh@inai.de>
Cc: "Alexander A. Klimov" <grandmaster@al2klimov.de>,
David Howells <dhowells@redhat.com>,
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,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: Good idea to rename files in include/uapi/ ?
Date: Mon, 22 Jun 2020 14:07:07 +0200 [thread overview]
Message-ID: <20200622120707.GA17620@salvia> (raw)
Message-ID: <20200622120707.Xm097DM-sT6EILb-N4oRnzK4oOqhW6nWUwacnujprE4@z> (raw)
In-Reply-To: <nycvar.YFH.7.77.849.2006221336180.26495@n3.vanv.qr>
On Mon, Jun 22, 2020 at 01:37:09PM +0200, Jan Engelhardt wrote:
>
> On Monday 2020-06-15 01:34, Alexander A. Klimov wrote:
> >>
> >> A header file rename is no problem. We even have dummy headers
> > Hmm.. if I understand all of you correctly, David, Stefano, Pablo and Al say
> > like no, not a good idea, but only you, Jan, say like should be no problem.
> >
> > Jan, do you have anything like commit messages in mainline or public emails
> > from maintainers confirming your opinion?
>
> I had already given the commit with the (email) message:
>
> >> Just look at xt_MARK.h, all it does is include xt_mark.h. Cf.
> >> 28b949885f80efb87d7cebdcf879c99db12c37bd .
Why rename this in 2020 ?
next prev parent reply other threads:[~2020-06-22 12:07 UTC|newest]
Thread overview: 26+ 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 19:41 ` Alexander A. Klimov
2020-06-14 20:19 ` David Howells
2020-06-14 20:19 ` David Howells
2020-06-14 21:08 ` Jan Engelhardt
2020-06-14 21:08 ` Jan Engelhardt
2020-06-14 22:01 ` Pablo Neira Ayuso
2020-06-14 22:01 ` Pablo Neira Ayuso
2020-06-14 23:34 ` Alexander A. Klimov
2020-06-14 23:34 ` Alexander A. Klimov
2020-06-22 11:37 ` Jan Engelhardt
2020-06-22 11:37 ` Jan Engelhardt
2020-06-22 12:07 ` Pablo Neira Ayuso [this message]
2020-06-22 12:07 ` Pablo Neira Ayuso
2020-06-22 18:06 ` Alexander A. Klimov
2020-06-22 18:06 ` Alexander A. Klimov
2020-06-14 20:34 ` Stefano Brivio
2020-06-14 20:34 ` Stefano Brivio
2020-06-14 23:07 ` Alexander A. Klimov
2020-06-14 23:07 ` Alexander A. Klimov
2020-06-15 11:11 ` Geert Uytterhoeven
2020-06-15 11:11 ` Geert Uytterhoeven
2020-06-14 22:47 ` Al Viro
2020-06-14 22:47 ` Al Viro
2020-06-15 11:12 ` Geert Uytterhoeven
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=20200622120707.GA17620@salvia \
--to=pablo@netfilter.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=coreteam@netfilter.org \
--cc=davem@davemloft.net \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=fw@strlen.de \
--cc=grandmaster@al2klimov.de \
--cc=j.alglave@ucl.ac.uk \
--cc=jengelh@inai.de \
--cc=kadlec@netfilter.org \
--cc=kuba@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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.