From: Willy Tarreau <[email protected]>
To: Linus Torvalds <[email protected]>
Cc: "Paul E. McKenney" <[email protected]>,
Linux Kernel Mailing List <[email protected]>,
Kernel Team <[email protected]>
Subject: Re: [GIT PULL] nolibc changes for v5.19
Date: Mon, 23 May 2022 22:50:43 +0200 [thread overview]
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHk-=wiX8P8atcx9at_N=-8pjU-d5cG509E=oZHfsVb1R41RZQ@mail.gmail.com>
On Mon, May 23, 2022 at 01:30:37PM -0700, Linus Torvalds wrote:
> On Mon, May 23, 2022 at 1:23 PM Willy Tarreau <[email protected]> wrote:
> >
> > So I've figured it again. When you run:
> >
> > make tools/help
> >
> > you get the help of tools/ commands, [..]
>
> You speak the words, but you don't actually look at what it does.
>
> Try it.
Why are you saying this ? I've figured the commands by trying
each of them.
> Yes, "make tools/help" works. Yes, it lists targets, and talks about
> how you can use the "<tool>_install" target.
>
> But none of that then matches the rest of what you write.
>
> You talk about nolibc_headers". That's not something that is actually
> listed in the help at all.
I agree. I initially added the few of them there and figured I was
polluting the "make tools/help" output with only nolibc-specific stuff.
I had a look at other comamnds that took arguments and found some that
would also take a few arguments that were not mentioned at the top level
so I concluded that it was the "expected" way to use them there.
> So please, can you read your own email message as somebody who doesn't
> actually know the code, and try the commands you talk about, and see
> the disconnect here?
That's exactly what I'm trying to do and I'm sorry if that doesn't work.
The simple fact that it doesn't work tells me I need to revisit the
approach but I need some hints about it. Please be more specific. I
tried to get as close as possible to what I found in order to apply the
principle of least surprise. Do you want me to create a "noblic_install"
target maybe, even if the equivalent one doesn't exist for half of the
other commands ? If that's it, that can be done as well.
Confused,
Willy
next prev parent reply other threads:[~2022-05-23 20:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-20 18:24 [GIT PULL] nolibc changes for v5.19 Paul E. McKenney
2022-05-23 18:42 ` Linus Torvalds
2022-05-23 19:56 ` Willy Tarreau
2022-05-23 20:23 ` Willy Tarreau
2022-05-23 20:30 ` Linus Torvalds
2022-05-23 20:50 ` Willy Tarreau [this message]
2022-05-23 21:04 ` Willy Tarreau
2022-05-23 21:13 ` Linus Torvalds
2022-05-23 22:01 ` Willy Tarreau
2022-05-23 19:20 ` pr-tracker-bot
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 \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
[email protected] \
/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