public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: jistone@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-0.9.9-219-g4569f6b
Date: Tue, 01 Sep 2009 16:47:00 -0000	[thread overview]
Message-ID: <20090901164712.2632.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  4569f6bb769482d732f72fb1208522d51f4e36f4 (commit)
      from  2649e13ce4e304e962049b25d07c9c522d5b5be3 (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 4569f6bb769482d732f72fb1208522d51f4e36f4
Author: Josh Stone <jistone@redhat.com>
Date:   Tue Sep 1 09:38:12 2009 -0700

    PR10581: Use ARCH for tracepoints and kernel typequeries
    
    These are kernel modules that we generate for querying debuginfo, so
    they need to use the same ARCH settings that we put in the main script
    module.
    
    * buildrun.cxx (make_tracequery, make_typequery_kmod): Add the arch and
      kbuild flags to make_cmd.
    * hash.cxx (find_stapconf_hash, find_tracequery_hash,
      find_typequery_hash): The arch is in the base hash already, but add
      the kbuild flags too.

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

Summary of changes:
 buildrun.cxx |   16 ++++++++++++++++
 hash.cxx     |   14 +++++++++++++-
 2 files changed, 29 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2009-09-01 16: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:
  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=20090901164712.2632.qmail@sourceware.org \
    --to=jistone@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).