public inbox for
help / color / mirror / Atom feed
Subject: [SCM]  master: Add bugzilla #'s to log, add item on hover-over variable fix.
Date: Fri, 06 Jun 2008 19:47:00 -0000	[thread overview]
Message-ID: <> (raw)

The branch, master has been updated
       via  2dd0f7cccb6b3ab1ee506033388fa083b342d507 (commit)
      from  d457d47661f4f6f233456e7f2ec24a94a79b2f90 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email.

- Log -----------------------------------------------------------------
commit 2dd0f7cccb6b3ab1ee506033388fa083b342d507
Author: Rick Moseley <>
Date:   Fri Jun 6 14:46:30 2008 -0500

    Add bugzilla #'s to log, add item on hover-over variable fix.
    * News: Add bugzilla #'s to log, add item on hover-over variable fix.


Summary of changes:
 NEWS                |    3 +++
 frysk-top/ChangeLog |    4 ++++
 2 files changed, 7 insertions(+), 0 deletions(-)

First 500 lines of diff:
diff --git a/NEWS b/NEWS
index 6403ca0..1a4ba4f 100644
--- a/NEWS
+++ b/NEWS
@@ -29,11 +29,14 @@ Release 0.4, ????-??-??
    when a "start" or "run" command is issued with no overriding
    parameters.  Also, on subsequent runs, "-la" is always used unless
    other parameters are entered with the "run" or "start" command.
+   (This was bz #6515/6536).
 -> Support was added for fully-qualified symbol notation using the
    standard HPD "#" syntax (e.g. "").  Ftrace now
    uses this notation to communicate with the user in both directions,
    FHPD recognizes the syntax although can't handle it yet.
+-> Fix Hover-over variable does not show variable value(bz #6484).
diff --git a/frysk-top/ChangeLog b/frysk-top/ChangeLog
index dcb5e9d..00498f2 100644
--- a/frysk-top/ChangeLog
+++ b/frysk-top/ChangeLog
@@ -1,3 +1,7 @@
+2008-06-06  Rick Moseley  <>
+	* NEWS: Add bz #'s; add item on hover-over variable.
 2008-06-04  Teresa Thomas  <>
 	* NEWS: Mention watching doubles, arrays.

frysk system monitor/debugger

                 reply	other threads:[~2008-06-06 19:47 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

* 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).