public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "fweimer at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sourceware.org
Subject: [Bug network/12154] Cannot resolve hosts which have wildcard aliases
Date: Tue, 30 Aug 2022 08:15:35 +0000	[thread overview]
Message-ID: <bug-12154-131-W96FZwUbhd@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-12154-131@http.sourceware.org/bugzilla/>

https://sourceware.org/bugzilla/show_bug.cgi?id=12154

Florian Weimer <fweimer at redhat dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|---                         |FIXED
   Target Milestone|---                         |2.37
             Status|ASSIGNED                    |RESOLVED

--- Comment #17 from Florian Weimer <fweimer at redhat dot com> ---
Fixed for glibc 2.37.

-- 
You are receiving this mail because:
You are on the CC list for the bug.

  parent reply	other threads:[~2022-08-30  8:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-22 14:17 [Bug libc/12154] New: Can not resolve chained CNAME with a wildcard among the chained CNAME vincent.viallet at gmail dot com
2010-10-22 14:51 ` [Bug libc/12154] " vincent.viallet at gmail dot com
2010-11-20 14:21 ` pasky at suse dot cz
2012-02-21  2:11 ` [Bug network/12154] " jsm28 at gcc dot gnu.org
2012-12-19 10:45 ` schwab@linux-m68k.org
2014-06-30  7:23 ` fweimer at redhat dot com
2022-07-04 16:17 ` [Bug network/12154] Cannot resolve hosts which have wildcard aliases fweimer at redhat dot com
2022-08-10  9:35 ` fweimer at redhat dot com
2022-08-30  8:04 ` cvs-commit at gcc dot gnu.org
2022-08-30  8:04 ` cvs-commit at gcc dot gnu.org
2022-08-30  8:15 ` fweimer at redhat dot com [this message]
2022-08-31  1:34 ` vincent.viallet at gmail dot com
2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org
2022-09-13 11:23 ` cvs-commit at gcc dot gnu.org
2022-09-13 11:24 ` cvs-commit at gcc dot gnu.org
2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org
2022-09-20 11:07 ` cvs-commit at gcc dot gnu.org
2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org
2022-09-21 18:01 ` cvs-commit at gcc dot gnu.org
2024-02-26 21:31 ` fw at deneb dot enyo.de
2024-02-27 11:07 ` fw at deneb dot enyo.de

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=bug-12154-131-W96FZwUbhd@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=glibc-bugs@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).