linux-sctp.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Philipp Stanner <stanner@posteo.de>
Cc: Willem de Bruijn <willemdebruijn.kernel@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Alexandra Winter <wintera@linux.ibm.com>,
	Thorsten Winkler <twinkler@linux.ibm.com>,
	David Ahern <dsahern@kernel.org>, Jay Vosburgh <jv@jvosburgh.net>,
	Andy Gospodarek <andy@greyhouse.net>,
	Subash Abhinov Kasiviswanathan <quic_subashab@quicinc.com>,
	Sean Tranchetti <quic_stranche@quicinc.com>,
	Paul Moore <paul@paul-moore.com>,
	Krzysztof Kozlowski <krzk@kernel.org>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Cong Wang <xiyou.wangcong@gmail.com>,
	Jiri Pirko <jiri@resnulli.us>,
	Marcelo Ricardo Leitner <marcelo.leitner@gmail.com>,
	Xin Long <lucien.xin@gmail.com>, Martin Schiller <ms@dev.tdt.de>,
	netdev@vger.kernel.org, linux-s390@vger.kernel.org,
	linux-security-module@vger.kernel.org,
	linux-sctp@vger.kernel.org, linux-x25@vger.kernel.org
Subject: Re: [PATCH net-next 00/13] net: header and core spelling corrections
Date: Sun, 25 Aug 2024 09:54:26 +0100	[thread overview]
Message-ID: <20240825085426.GY2164@kernel.org> (raw)
In-Reply-To: <d15e45f17dcb9c98664590711ac874302a7e6689.camel@posteo.de>

On Sun, Aug 25, 2024 at 07:52:45AM +0000, Philipp Stanner wrote:
> Am Donnerstag, dem 22.08.2024 um 13:57 +0100 schrieb Simon Horman:
> > This patchset addresses a number of spelling errors in comments in
> > Networking files under include/, and files in net/core/. Spelling
> > problems are as flagged by codespell.
> > 
> > It aims to provide patches that can be accepted directly into net-
> > next.
> > And splits patches up based on maintainer boundaries: many things
> > feed directly into net-next. This is a complex process and I
> > apologise
> > for any errors.
> 
> Are you aware that this lessens git blame's ability to provide the
> latest relevant change and associated commit message?
> 
> Many software projects suffer from whitespace and spelling fixes
> preventing git blame from figuring out years later what original code
> was intended to do.
> 
> I'd consider that improving spelling might not win that cost-benefit-
> ratio.

Sure, that is a judgment call that can be made.  I think that it is pretty
common for spelling corrections to be accepted, and I do think there is a
value in having things spelt correctly.  But if the consensus is otherwise,
then fine.

  parent reply	other threads:[~2024-08-25  8:54 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-22 12:57 [PATCH net-next 00/13] net: header and core spelling corrections Simon Horman
2024-08-22 12:57 ` [PATCH net-next 01/13] packet: Correct spelling in if_packet.h Simon Horman
2024-08-23 12:42   ` Willem de Bruijn
2024-08-22 12:57 ` [PATCH net-next 02/13] s390/iucv: Correct spelling in iucv.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 03/13] ip_tunnel: Correct spelling in ip_tunnels.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 04/13] ipv6: Correct spelling in ipv6.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 05/13] bonding: Correct spelling in headers Simon Horman
2024-08-22 12:57 ` [PATCH net-next 06/13] net: qualcomm: rmnet: Correct spelling in if_rmnet.h Simon Horman
2024-08-23  5:07   ` Subash Abhinov Kasiviswanathan (KS)
2024-08-22 12:57 ` [PATCH net-next 07/13] netlabel: Correct spelling in netlabel.h Simon Horman
2024-08-22 12:57 ` [PATCH net-next 08/13] NFC: Correct spelling in headers Simon Horman
2024-08-23 13:40   ` Krzysztof Kozlowski
2024-08-22 12:57 ` [PATCH net-next 09/13] net: sched: " Simon Horman
2024-08-22 12:57 ` [PATCH net-next 10/13] sctp: " Simon Horman
2024-08-22 14:01   ` Xin Long
2024-08-22 12:57 ` [PATCH net-next 11/13] x25: Correct spelling in x25.h Simon Horman
2024-08-23  5:27   ` Martin Schiller
2024-08-22 12:57 ` [PATCH net-next 12/13] net: Correct spelling in headers Simon Horman
2024-08-26 16:45   ` Jakub Kicinski
2024-08-27  8:25     ` Simon Horman
2024-08-22 12:57 ` [PATCH net-next 13/13] net: Correct spelling in net/core Simon Horman
2024-08-25  7:52 ` [PATCH net-next 00/13] net: header and core spelling corrections Philipp Stanner
2024-08-25  8:06   ` Krzysztof Kozlowski
2024-08-25  8:54   ` Simon Horman [this message]
2024-08-26 16:50 ` patchwork-bot+netdevbpf

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=20240825085426.GY2164@kernel.org \
    --to=horms@kernel.org \
    --cc=andy@greyhouse.net \
    --cc=davem@davemloft.net \
    --cc=dsahern@kernel.org \
    --cc=edumazet@google.com \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=jv@jvosburgh.net \
    --cc=krzk@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=linux-sctp@vger.kernel.org \
    --cc=linux-security-module@vger.kernel.org \
    --cc=linux-x25@vger.kernel.org \
    --cc=lucien.xin@gmail.com \
    --cc=marcelo.leitner@gmail.com \
    --cc=ms@dev.tdt.de \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=paul@paul-moore.com \
    --cc=quic_stranche@quicinc.com \
    --cc=quic_subashab@quicinc.com \
    --cc=stanner@posteo.de \
    --cc=twinkler@linux.ibm.com \
    --cc=willemdebruijn.kernel@gmail.com \
    --cc=wintera@linux.ibm.com \
    --cc=xiyou.wangcong@gmail.com \
    /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).