From: "fche at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sourceware.org
Subject: [Bug documentation/27186] Document CONTEXT variable in embedded C docs
Date: Fri, 15 Jan 2021 23:04:09 +0000 [thread overview]
Message-ID: <bug-27186-6586-gejbyagRV5@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-27186-6586@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=27186
Frank Ch. Eigler <fche at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |WAITING
Ever confirmed|0 |1
CC| |fche at redhat dot com
Last reconfirmed| |2021-01-15
--- Comment #1 from Frank Ch. Eigler <fche at redhat dot com> ---
forgot to attach!
--
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2021-01-15 23:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-15 1:55 [Bug documentation/27186] New: " craig.ringer at 2ndquadrant dot com
2021-01-15 1:56 ` [Bug documentation/27186] " craig.ringer at 2ndquadrant dot com
2021-01-15 23:04 ` fche at redhat dot com [this message]
2021-01-18 3:29 ` craig.ringer at 2ndquadrant dot com
2021-01-25 22:56 ` fche at redhat dot com
2021-01-29 11:17 ` craig.ringer at 2ndquadrant 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-27186-6586-gejbyagRV5@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).