From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug translator/10280] allow relaxing of `uname -r` matching runtime assertion
Date: Sun, 14 Jun 2009 15:00:00 -0000 [thread overview]
Message-ID: <20090614150020.19457.qmail@sourceware.org> (raw)
In-Reply-To: <20090614144100.10280.fche@redhat.com>
------- Additional Comments From fche at redhat dot com 2009-06-14 15:00 -------
Oh dear, UTS_RELEASE is a compile-time value rather than a run-time value
in some cases, so the check currently there doesn't accomplish very much
at all.
--
http://sourceware.org/bugzilla/show_bug.cgi?id=10280
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2009-06-14 15:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-14 14:41 [Bug translator/10280] New: " fche at redhat dot com
2009-06-14 15:00 ` fche at redhat dot com [this message]
2009-07-02 13:55 ` [Bug translator/10280] allow relaxing of `uname -r` matching runtime assertion ro ABI-compatible kernel series fche at redhat dot com
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=20090614150020.19457.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@sources.redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).