public inbox for frysk-bugzilla@sourceware.org
help / color / mirror / Atom feed
From: "cagney at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: frysk-bugzilla@sourceware.org
Subject: [Bug general/4163] create custom observer double step
Date: Fri, 16 Mar 2007 16:36:00 -0000	[thread overview]
Message-ID: <20070316163619.7206.qmail@sourceware.org> (raw)
In-Reply-To: <20070306220819.4163.cagney@redhat.com>


------- Additional Comments From cagney at redhat dot com  2007-03-16 16:36 -------
Yes, concept of "create a custom observer" has morphed into "customize
observer".  For instance, for syscall-observer, customizing it to just record
specific system calls.

This in turn, though, leads to further questions:

-> what happens if I click on "Syscall Observer" and then click "customize"; is
it customizing just the local systemcall observer, or globally.

I'm guessing that a customization would apply locally.

Perhaps edit, copy buttons are the way to go?
Perhaps the interface could better suggest that the observers are being added to
a local copy of the pool; for instance (but don't follow :-) the proc-picker
makes it clear which processes are of interest by copying them into a separate
window


-- 


http://sourceware.org/bugzilla/show_bug.cgi?id=4163

------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.


  parent reply	other threads:[~2007-03-16 16:36 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-06 22:08 [Bug general/4163] New: " cagney at redhat dot com
2007-03-14 18:44 ` [Bug general/4163] " swagiaal at redhat dot com
2007-03-16 16:36 ` cagney at redhat dot com [this message]
2007-03-16 20:46 ` swagiaal at redhat dot com
2007-03-26 18:09 ` swagiaal 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=20070316163619.7206.qmail@sourceware.org \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=frysk-bugzilla@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).