From: Peter Korsgaard <peter@korsgaard.com>
To: <Eugen.Hristev@microchip.com>
Cc: fontaine.fabrice@gmail.com, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/dhcp: use internal bind
Date: Tue, 12 Apr 2022 14:34:19 +0200 [thread overview]
Message-ID: <87y20aeb04.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <34fddc8f-8710-65f9-330d-81fefe64354a@microchip.com> (Eugen Hristev's message of "Tue, 12 Apr 2022 11:43:10 +0000")
>>>>> <Eugen.Hristev@microchip.com> writes:
Hi,
>> Yeah. Eugen, is there any specific reason why you use the dhcp package
>> over the other DHCP clients we provide?
> Historical reasons, and the fact that people have working configurations
> using this package... I was unaware that it was due to be removed.
> We will try to switch to a different package in the future. Thanks for
> letting me know.
> However, if the package is still in this buildroot release, it has to
> work right ?
Yes, that is the idea. If it is dead upstream and hard to fix then that
naturally makes it harder to do, but the intention is to fix it.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-04-12 12:34 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-03 10:03 [Buildroot] [PATCH 1/1] package/dhcp: use internal bind Fabrice Fontaine
2022-04-04 6:19 ` James Hilliard
2022-04-04 19:31 ` Arnout Vandecappelle
2022-04-04 19:55 ` Yann E. MORIN
2022-04-09 14:09 ` Peter Korsgaard
2022-04-12 11:15 ` Eugen.Hristev--- via buildroot
2022-04-12 11:22 ` Fabrice Fontaine
2022-04-12 11:33 ` Peter Korsgaard
2022-04-12 11:43 ` Eugen.Hristev--- via buildroot
2022-04-12 12:32 ` Eugen.Hristev--- via buildroot
2022-04-12 12:34 ` Peter Korsgaard [this message]
2022-04-12 18:17 ` Fabrice Fontaine
2022-04-13 7:54 ` Eugen.Hristev--- via buildroot
2022-04-13 8:29 ` Peter Korsgaard
2022-04-14 9:10 ` Eugen.Hristev--- via buildroot
2022-04-14 9:59 ` Fabrice Fontaine
2022-04-14 16:44 ` Fabrice Fontaine
2022-04-19 5:21 ` Eugen.Hristev--- via buildroot
2022-04-19 9:08 ` Fabrice Fontaine
2022-04-19 10:19 ` Eugen.Hristev--- via buildroot
2022-04-19 16:12 ` Fabrice Fontaine
2022-04-21 9:25 ` Eugen.Hristev--- via buildroot
-- strict thread matches above, loose matches on Subject: below --
2022-04-04 13:07 Edmundo Ferreira
2022-04-05 3:54 Tim Hammer
2022-04-05 6:19 ` Fabrice Fontaine
2022-04-05 12:15 ` Tim Hammer
2022-04-05 16:18 ` Peter Seiderer
2022-04-06 1:58 ` Tim Hammer
2022-04-06 7:08 ` Fabrice Fontaine
2022-04-06 12:58 ` Tim Hammer
2022-04-06 13:30 ` Fabrice Fontaine
2022-04-06 14:06 ` Fabrice Fontaine
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=87y20aeb04.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=Eugen.Hristev@microchip.com \
--cc=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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