From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: Julien Olivain <ju.o@free.fr>,
Peter Korsgaard <jacmet@uclibc.org>,
Romain Naour <romain.naour@smile.fr>,
buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/procps-ng: fix typos in config option and help text
Date: Tue, 29 Oct 2024 14:38:39 +0100 [thread overview]
Message-ID: <20241029143839.0d7c0e33@windsurf> (raw)
In-Reply-To: <CAFkzVZbMnTyfy2VfrNY0Pb4-Xi=MDmuGvgyvpk-rBns3NO8N+w@mail.gmail.com>
On Tue, 29 Oct 2024 21:34:18 +0800
Scott Fan <fancp2007@gmail.com> wrote:
> > Thanks for spotting this. However, since this option has made its way
> > to Buildroot 2024.08, I think we have no choice but to add an entry in
> > the Config.in.legacy file for the old option name.
> I found, no defconfig file has used this option so far.
defconfigs in Buildroot upstream are not the problem, as anyway our
upstream defconfigs are minimal so none of them will ever enable
procps-ng.
We are concerned about all the custom configurations/defconfigs that
people have created for their own projects. This is why we have
Config.in.legacy in the first place.
Best regards,
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-10-29 13:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-29 4:48 [Buildroot] [PATCH] package/procps-ng: fix typos in config option and help text Scott Fan
2024-10-29 11:21 ` Thomas Petazzoni via buildroot
2024-10-29 13:34 ` Scott Fan
2024-10-29 13:38 ` Thomas Petazzoni via buildroot [this message]
2024-10-29 13:58 ` [Buildroot] [PATCH v2] " Scott Fan
2024-10-29 14:11 ` [Buildroot] [PATCH v3] " Scott Fan
2024-10-29 17:49 ` Thomas Petazzoni via buildroot
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=20241029143839.0d7c0e33@windsurf \
--to=buildroot@buildroot.org \
--cc=fancp2007@gmail.com \
--cc=jacmet@uclibc.org \
--cc=ju.o@free.fr \
--cc=romain.naour@smile.fr \
--cc=thomas.petazzoni@bootlin.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