public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: brolley@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.0-204-g7885012
Date: Tue, 10 Nov 2009 17:17:00 -0000	[thread overview]
Message-ID: <20091110171754.20500.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  7885012ba0a7c1d7c974dd9528afa90aeed916a6 (commit)
      from  3d3942f6b1ccb9062794527f2f204d98642eaed2 (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 7885012ba0a7c1d7c974dd9528afa90aeed916a6
Author: Dave Brolley <brolley@redhat.com>
Date:   Tue Nov 10 12:12:54 2009 -0500

    Replace the use of the global variable 'modpath' in diagnostic
    messages within verify_it with the use of a 'module_name'
    parameter passed in.
    
    Add a comment in insert_module explaining why it's ok to
    overwrite the 'path' parameter with the canonicalized path.

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

Summary of changes:
 runtime/staprun/modverify.c     |   15 ++++++++-------
 runtime/staprun/modverify.h     |    3 ++-
 runtime/staprun/staprun_funcs.c |    6 ++++--
 3 files changed, 14 insertions(+), 10 deletions(-)


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


                 reply	other threads:[~2009-11-10 17:17 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=20091110171754.20500.qmail@sourceware.org \
    --to=brolley@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).