From: "Tom Schwindl" <schwindl@posteo.de>
To: "Alejandro Colomar" <alx.manpages@gmail.com>,
"Oskari Pirhonen" <xxc3ncoredxx@gmail.com>,
"Sam James" <sam@gentoo.org>
Cc: <linux-man@vger.kernel.org>,
"Guillem Jover" <guillem@hadrons.org>,
"Brian Inglis" <Brian.Inglis@Shaw.ca>,
"Matt Jolly" <Matt.Jolly@footclan.ninja>
Subject: Re: [PATCH v2] stdc: some improvements
Date: Fri, 24 Mar 2023 12:46:31 +0000 [thread overview]
Message-ID: <CREMHEG9VJ7R.2DKYU7GIT4J8V@morphine> (raw)
In-Reply-To: <a16c019b-66dd-adc1-769c-8a6fb813e288@gmail.com>
> > +
> > +# vim: set noexpandtab:
>
> I'm not sure we want vim comments like this one for every file. Aren't
> they too noisy? But maybe it's just me. I use things like the following
> for when I contribute regularly to projects that use a different rule for
> indentation:
>
I second this. Vim comments pollute source files and are way too editor
specific. It's also questionable if they're that useful. If someone sends
a patch with spaces instead of tabs, that's easy to catch and fix.
--
Best Regards,
Tom Schwindl
next prev parent reply other threads:[~2023-03-24 12:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 5:07 [PATCH v2] stdc: some improvements Oskari Pirhonen
2023-03-24 12:21 ` Alejandro Colomar
2023-03-24 12:46 ` Tom Schwindl [this message]
2023-03-25 5:08 ` Oskari Pirhonen
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=CREMHEG9VJ7R.2DKYU7GIT4J8V@morphine \
--to=schwindl@posteo.de \
--cc=Brian.Inglis@Shaw.ca \
--cc=Matt.Jolly@footclan.ninja \
--cc=alx.manpages@gmail.com \
--cc=guillem@hadrons.org \
--cc=linux-man@vger.kernel.org \
--cc=sam@gentoo.org \
--cc=xxc3ncoredxx@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