From: "Lars R. Damerow" <lars@pixar.com>
To: Josh Stone <jistone@redhat.com>
Cc: "systemtap@sourceware.org" <systemtap@sourceware.org>
Subject: Re: [Bug runtime/6562] $SYSTEMTAP_DEBUGINFO_PATH does not work
Date: Wed, 19 Mar 2014 23:35:00 -0000 [thread overview]
Message-ID: <76B28FBD-2548-46EF-9F48-F94BE27DF67F@pixar.com> (raw)
In-Reply-To: <532A266E.9080905@redhat.com>
Yep, that's what happened. I glanced at the resulting page after my comment and saw "REOPENED", which made me think I'd done something bad.
What weird default behavior. Thanks for the tip and sorry for my confusion!
> On Mar 19, 2014, at 16:21, Josh Stone <jistone@redhat.com> wrote:
>
>> On 03/19/2014 03:21 PM, lars at pixar dot com wrote:
>> https://sourceware.org/bugzilla/show_bug.cgi?id=6562
>>
>> Lars R. Damerow <lars at pixar dot com> changed:
>>
>> What |Removed |Added
>> ----------------------------------------------------------------------------
>> CC| |lars at pixar dot com
>>
>> --- Comment #16 from Lars R. Damerow <lars at pixar dot com> ---
>> Argh, didn't realize commenting would reopen. Sorry about that.
>
> Lars,
>
> I assume you're talking about your PR16719 comment; note this second
> comment is on PR6562. You haven't affect the status of either.
>
> Consider changing the bugzilla preference for "After changing a bug:" to
> "Show the updated bug". The default is "Show the next bug in my list",
> which I find is rarely what I want.
>
> Josh
>
next prev parent reply other threads:[~2014-03-19 23:35 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-6562-6586@http.sourceware.org/bugzilla/>
2014-03-19 22:21 ` lars at pixar dot com
2014-03-19 23:21 ` Josh Stone
2014-03-19 23:35 ` Lars R. Damerow [this message]
2021-08-30 16:48 ` fche at redhat dot com
2008-05-27 1:34 [Bug runtime/6562] New: " prasad at linux dot vnet dot ibm dot com
2008-05-27 19:31 ` [Bug runtime/6562] " wenji dot huang at oracle dot com
2008-05-27 19:41 ` prasad at linux dot vnet dot ibm dot com
2008-05-28 16:57 ` srinivasa at in dot ibm dot com
2008-05-28 17:20 ` fche at redhat dot com
2008-05-28 17:24 ` ananth at in dot ibm dot com
2008-05-29 12:17 ` srinivasa at in dot ibm dot com
2008-05-29 12:23 ` ananth at in dot ibm dot com
2008-06-03 23:41 ` fche at redhat dot com
2008-07-10 16:49 ` fche at redhat dot com
2008-07-11 3:23 ` wenji dot huang at oracle dot com
2008-07-11 10:47 ` srinivasa at in dot ibm dot com
2008-10-20 15:15 ` fche at redhat dot com
2008-10-20 18:59 ` mjw at redhat dot com
2008-10-21 6:33 ` srinivasa at in dot ibm dot com
2009-02-03 5:36 ` srikar at linux dot vnet dot ibm dot com
2009-02-03 6:08 ` srikar at linux dot vnet dot ibm 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=76B28FBD-2548-46EF-9F48-F94BE27DF67F@pixar.com \
--to=lars@pixar.com \
--cc=jistone@redhat.com \
--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).