From: "Thomas Weißschuh " <thomas@t-8ch.de>
To: Willy Tarreau <w@1wt.eu>
Cc: "Thomas Weißschuh" <linux@weissschuh.net>,
"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 20:23:39 +0200 (GMT+02:00) [thread overview]
Message-ID: <dc079808-ef49-42b6-9147-b043b97dcc86@t-8ch.de> (raw)
In-Reply-To: <20240803100318.GG29127@1wt.eu>
Aug 3, 2024 12:03:27 Willy Tarreau <w@1wt.eu>:
> 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 ;-)
Complete Ack :-)
I tend to become lazy when I feel to get away with it.
Thanks for calling me out on it.
> 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 ;-)
It's meticulously undocumented,
and a very fringe usecase.
I'll use your proposal, fill it with more background and apply it.
Thomas
prev parent reply other threads:[~2024-08-03 18:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-28 20:34 Thomas Weißschuh
2024-08-03 10:03 ` Willy Tarreau
2024-08-03 18:23 ` Thomas Weißschuh [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=dc079808-ef49-42b6-9147-b043b97dcc86@t-8ch.de \
--to=thomas@t-8ch.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux@weissschuh.net \
--cc=shuah@kernel.org \
--cc=w@1wt.eu \
/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
all inboxes | Powered by JetHome®