From: "dsmith at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: systemtap@sources.redhat.com
Subject: [Bug tapsets/10900] nfs tapset problems
Date: Mon, 09 Nov 2009 15:58:00 -0000 [thread overview]
Message-ID: <20091109155803.18710.qmail@sourceware.org> (raw)
In-Reply-To: <20091103222408.10900.dsmith@redhat.com>
------- Additional Comments From dsmith at redhat dot com 2009-11-09 15:58 -------
(In reply to comment #1)
> seems duplicate with #5150
Looks like it is.
*** This bug has been marked as a duplicate of 5150 ***
--
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |DUPLICATE
http://sourceware.org/bugzilla/show_bug.cgi?id=10900
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
prev parent reply other threads:[~2009-11-09 15:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-03 22:24 [Bug tapsets/10900] New: " dsmith at redhat dot com
2009-11-09 9:16 ` [Bug tapsets/10900] " wenji dot huang at oracle dot com
2009-11-09 15:58 ` dsmith at redhat dot com [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=20091109155803.18710.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).