* Re: Backport the stub resolver changes to 2.25?
2017-01-01 0:00 Backport the stub resolver changes to 2.25? Florian Weimer
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Carlos O'Donell
@ 2017-01-01 0:00 ` Andreas K. Huettel
2 siblings, 0 replies; 5+ messages in thread
From: Andreas K. Huettel @ 2017-01-01 0:00 UTC (permalink / raw)
To: libc-stable
On September 4, 2017 10:53:49 AM GMT+03:00, Florian Weimer <fweimer@redhat.com> wrote:
>Does anyone object to backporting the stub resolver changes (include
>automated /etc/resolv.conf reloading) to 2.25?
>
>Thanks,
>Florian
Afaicr we already use that in gentoo unstable
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Backport the stub resolver changes to 2.25?
2017-01-01 0:00 Backport the stub resolver changes to 2.25? Florian Weimer
2017-01-01 0:00 ` Florian Weimer
@ 2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Andreas K. Huettel
2 siblings, 0 replies; 5+ messages in thread
From: Carlos O'Donell @ 2017-01-01 0:00 UTC (permalink / raw)
To: Florian Weimer, Libc-stable Mailing List
On 09/04/2017 02:53 AM, Florian Weimer wrote:
> Does anyone object to backporting the stub resolver changes (include
> automated /etc/resolv.conf reloading) to 2.25?
The API/ABI is mostly preserved given the magic value checking you added
which means that this is just a behavioural change on an existing stable
branch.
Given that Gentoo and Debian are already using it downstream, and Fedora
would like to also, I don't see why we can't backport that to 2.25.
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 5+ messages in thread
* Backport the stub resolver changes to 2.25?
@ 2017-01-01 0:00 Florian Weimer
2017-01-01 0:00 ` Florian Weimer
` (2 more replies)
0 siblings, 3 replies; 5+ messages in thread
From: Florian Weimer @ 2017-01-01 0:00 UTC (permalink / raw)
To: Libc-stable Mailing List
Does anyone object to backporting the stub resolver changes (include
automated /etc/resolv.conf reloading) to 2.25?
Thanks,
Florian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Backport the stub resolver changes to 2.25?
2017-01-01 0:00 Backport the stub resolver changes to 2.25? Florian Weimer
@ 2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Andreas K. Huettel
2 siblings, 1 reply; 5+ messages in thread
From: Florian Weimer @ 2017-01-01 0:00 UTC (permalink / raw)
To: libc-stable
On 09/04/2017 09:53 AM, Florian Weimer wrote:
> Does anyone object to backporting the stub resolver changes (include
> automated /etc/resolv.conf reloading) to 2.25?
The straightforward backport involves more than 80 patches, so I don't
think it's applicable for upstream. The backport is available in Fedora
26, though.
Florian
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Backport the stub resolver changes to 2.25?
2017-01-01 0:00 ` Florian Weimer
@ 2017-01-01 0:00 ` Carlos O'Donell
0 siblings, 0 replies; 5+ messages in thread
From: Carlos O'Donell @ 2017-01-01 0:00 UTC (permalink / raw)
To: Florian Weimer, libc-stable
On 10/11/2017 07:08 AM, Florian Weimer wrote:
> On 09/04/2017 09:53 AM, Florian Weimer wrote:
>> Does anyone object to backporting the stub resolver changes
>> (include automated /etc/resolv.conf reloading) to 2.25?
>
> The straightforward backport involves more than 80 patches, so I
> don't think it's applicable for upstream. The backport is available
> in Fedora 26, though.
Thanks for the heads up.
--
Cheers,
Carlos.
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2017-10-11 16:48 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-01-01 0:00 Backport the stub resolver changes to 2.25? Florian Weimer
2017-01-01 0:00 ` Florian Weimer
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Carlos O'Donell
2017-01-01 0:00 ` Andreas K. Huettel
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).