From: Nikos Chantziaras <realnc@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: [gentoo-user] Re: linux-headers-4.19 & glibc
Date: Wed, 24 Jul 2019 19:13:21 +0300 [thread overview]
Message-ID: <qha031$4va$1@blaine.gmane.org> (raw)
In-Reply-To: <ce65a278-c026-43bf-93cc-591d80755104@email.android.com>
On 24/07/2019 16:49, Hasan ÇALIŞIR wrote:
> Today i got linux-headers-4.19 update.
>
> Doesn't it need re-building glibc that currently not triggered on my system?
Nope. No need.
prev parent reply other threads:[~2019-07-24 16:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 13:49 [gentoo-user] linux-headers-4.19 & glibc Hasan ÇALIŞIR
2019-07-24 16:13 ` Nikos Chantziaras [this message]
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='qha031$4va$1@blaine.gmane.org' \
--to=realnc@gmail.com \
--cc=gentoo-user@lists.gentoo.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