From: Willy Tarreau <w@1wt.eu>
To: "Thomas Weißschuh" <linux@weissschuh.net>
Cc: Shuah Khan <shuah@kernel.org>,
linux-kernel@vger.kernel.org, linux-kselftest@vger.kernel.org
Subject: Re: [PATCH] tools/nolibc: pass argc, argv and envp to constructors
Date: Sat, 3 Aug 2024 12:03:18 +0200 [thread overview]
Message-ID: <20240803100318.GG29127@1wt.eu> (raw)
In-Reply-To: <20240728-nolibc-constructor-args-v1-1-36d0bf5cd4c0@weissschuh.net>
On Sun, Jul 28, 2024 at 10:34:11PM +0200, Thomas Weißschuh wrote:
> Mirror glibc behavior for compatibility.
Generally speaking I think you should make a bit longer sentences in
your commit messages, Thomas. One first reason is to think that during
reviews the reviewer has to scroll up to find the subject for the context
this sentence applies to. And doing so quickly encourages to give a little
bit more background to justify a change. I have a simple principle that
works reasonably fine for this, which is that a commit subject should
normally be unique in a project (modulo rare cases, reverts or accidents)
and that commit message bodies should really always be unique. Here we
see that it doesn't work ;-)
An example could be something like this:
Glibc has been passing argc/argv/envp to constructors since version XXX.
This is particularly convenient, and missing it can significantly
complicate some ports to nolibc. Let's do the same since it's an easy
change that comes at no cost.
Anyway I agree with the change, I wasn't aware of this support from glibc,
so thank you for enlighting me on this one ;-)
Willy
next prev parent reply other threads:[~2024-08-03 10:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 20:34 [PATCH] tools/nolibc: pass argc, argv and envp to constructors Thomas Weißschuh
2024-08-03 10:03 ` Willy Tarreau [this message]
2024-08-03 18:23 ` Thomas Weißschuh
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=20240803100318.GG29127@1wt.eu \
--to=w@1wt.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@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