public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-320-gd124d4d
Date: Tue, 18 Oct 2011 12:44:00 -0000	[thread overview]
Message-ID: <20111018124411.17488.qmail@sourceware.org> (raw)

This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "systemtap: system-wide probe/trace tool".

The branch, master has been updated
       via  d124d4decd2e1ab45727f2b4d9994a377998cb41 (commit)
      from  c12bdeab8e5515848ba0d2af21c8c6e5c072c42a (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit d124d4decd2e1ab45727f2b4d9994a377998cb41
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Oct 18 14:28:59 2011 +0200

    PR13284 Failure to resolve kernel global e.g. jiffies.
    
    * dwflpp.cxx (vardie_from_symtable): Also accept STT_NOTYPE. Some global
      don't have a type associated with them.
    * testsuite/buildok/pr13284.stp: New testcase.

-----------------------------------------------------------------------

Summary of changes:
 dwflpp.cxx                    |    3 ++-
 testsuite/buildok/pr13284.stp |    4 ++++
 2 files changed, 6 insertions(+), 1 deletions(-)
 create mode 100644 testsuite/buildok/pr13284.stp


hooks/post-receive
--
systemtap: system-wide probe/trace tool


                 reply	other threads:[~2011-10-18 12:44 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:
  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=20111018124411.17488.qmail@sourceware.org \
    --to=mark@sourceware.org \
    --cc=systemtap-cvs@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).