From: "libo.ch at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug translator/6711] need script syntax for extending blacklist
Date: Wed, 31 May 2023 02:01:59 +0000 [thread overview]
Message-ID: <bug-6711-6586-hdYIP63I7L@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-6711-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=6711
--- Comment #11 from libo.ch at gmail dot com ---
Removed
fche at redhat dot com via Systemtap <systemtap@sourceware.org>
于2023年5月26日周五 04:50写道：
> https://sourceware.org/bugzilla/show_bug.cgi?id=6711
>
> Frank Ch. Eigler <fche at redhat dot com> changed:
>
> What |Removed |Added
>
> ----------------------------------------------------------------------------
> Status|NEW |RESOLVED
> Resolution|--- |OBSOLETE
>
> --- Comment #10 from Frank Ch. Eigler <fche at redhat dot com> ---
> no such serious need has arisen
>
> --
> You are receiving this mail because:
> You are the assignee for the bug.
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2023-05-31 2:02 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6711-6586@http.sourceware.org/bugzilla/>
2023-05-25 20:49 ` fche at redhat dot com
2023-05-31 2:01 ` libo.ch at gmail dot com [this message]
[not found] <20080630230203.6711.fche@redhat.com>
2008-08-28 18:41 ` mhiramat at redhat dot com
2010-01-19 8:49 ` wenji dot huang at oracle dot com
2010-01-19 12:00 ` fche at redhat dot com
2010-01-21 3:21 ` wenji dot huang at oracle dot com
2010-01-21 20:22 ` jistone at redhat dot com
2010-01-22 5:46 ` wenji dot huang at oracle dot com
2010-01-25 7:52 ` wenji dot huang at oracle dot com
2010-02-10 2:10 ` jistone at redhat dot com
2010-02-10 2:15 ` jistone 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=bug-6711-6586-hdYIP63I7L@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=systemtap@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).