From: "Cristian Rodríguez" <cristian@rodriguez.im>
To: Florian Weimer <fweimer@redhat.com>
Cc: John Levon <levon@movementarian.org>, libc-alpha@sourceware.org
Subject: Re: Issue with stale resolv.conf state
Date: Tue, 12 Mar 2024 11:25:01 -0300 [thread overview]
Message-ID: <CAPBLoAcZEz1hwAP++77qvhpHf7bZaKct3XS7APLR9O+EhghOJA@mail.gmail.com> (raw)
In-Reply-To: <87ttlcvth8.fsf@oldenburg.str.redhat.com>
On Tue, Mar 12, 2024 at 3:45 AM Florian Weimer <fweimer@redhat.com> wrote:
> So the solution might not be so straightforward.
I 'm not being sarcastic or anything.. but if the standards do not
recommend an approach for this.. I strongly suggest doing it like
Windows does.
next prev parent reply other threads:[~2024-03-12 14:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-11 9:08 John Levon
2024-03-11 10:51 ` Florian Weimer
2024-03-12 0:51 ` Cristian Rodríguez
2024-03-12 6:45 ` Florian Weimer
2024-03-12 9:09 ` Philip Sanetra
2024-03-12 10:04 ` John Levon
2024-03-12 14:25 ` Cristian Rodríguez [this message]
2024-03-12 14:30 ` Florian Weimer
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=CAPBLoAcZEz1hwAP++77qvhpHf7bZaKct3XS7APLR9O+EhghOJA@mail.gmail.com \
--to=cristian@rodriguez.im \
--cc=fweimer@redhat.com \
--cc=levon@movementarian.org \
--cc=libc-alpha@sourceware.org \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).