From: Sam James <sam@gentoo.org>
To: Jan Beulich <jbeulich@suse.com>
Cc: Jonas 'Sortie' Termansen <sortie@maxsi.org>,
binutils@sourceware.org, Nick Alcock <nick.alcock@oracle.com>
Subject: Re: [PATCH] Remove unnecessary non-standard & unportable inclusions.
Date: Tue, 05 Nov 2024 01:49:53 +0000 [thread overview]
Message-ID: <87cyja5u0u.fsf@gentoo.org> (raw)
In-Reply-To: <110a3cb4-a076-4633-ae67-d7780ebae92b@suse.com> (Jan Beulich's message of "Mon, 4 Nov 2024 09:01:45 +0100")
Jan Beulich <jbeulich@suse.com> writes:
> On 01.11.2024 21:26, Jonas 'Sortie' Termansen wrote:
>> <memory.h> is not needed and not standardized and is just an alias for
>> <string.h>.
>
> The question with such #include-s is virtually always: Are they there to
> work around issues on certain platforms (a detail which would imo be
> relevant to put in the patch description)? In the case here the line was
> present from the introduction of the helper tool, so that's hard to
> answer (may want to ask the author though, as it hasn't been _that_ long
> ago that the tool was introduced). On that basis I'd be okay to approve
> that change alone, while ...
>
>> <sys/param.h> is not needed and not standardized and contains a kitchen
>> sink of various unportable definitions not agreed upon and best done
>> manually or through other headers.
>
> ... I guess we will want Nick's input here, whom you didn't even Cc.
While I agree that this is a good idea and that people ought to do it,
projects often don't document that you should, and I don't think we're
an exception.
I don't see it at https://www.gnu.org/software/binutils/ or
https://sourceware.org/binutils/wiki/HowToContribute.
I'll add it to the latter. I dunno how to edit the former. Thanks.
prev parent reply other threads:[~2024-11-05 1:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 20:26 Jonas 'Sortie' Termansen
2024-11-04 8:01 ` Jan Beulich
2024-11-04 11:53 ` Jonas 'Sortie' Termansen
2024-11-04 12:51 ` Jan Beulich
2024-11-05 0:30 ` Nick Alcock
2024-11-05 1:49 ` Sam James [this message]
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=87cyja5u0u.fsf@gentoo.org \
--to=sam@gentoo.org \
--cc=binutils@sourceware.org \
--cc=jbeulich@suse.com \
--cc=nick.alcock@oracle.com \
--cc=sortie@maxsi.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 read-only IMAP folder(s) and NNTP newsgroup(s).