public inbox for
help / color / mirror / Atom feed
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.8-145-g3451624
Date: Mon, 06 Aug 2012 20:25:00 -0000	[thread overview]
Message-ID: <> (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  3451624dbc89d790afe9c0d2d6da4d9e3f7a766f (commit)
       via  5ecd69990a5136be2082f54604b77275a87e39dd (commit)
      from  1c0b8e238e7d30e76c725f192c6c31882b1b13f6 (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 3451624dbc89d790afe9c0d2d6da4d9e3f7a766f
Author: Josh Stone <>
Date:   Mon Aug 6 13:14:00 2012 -0700

    spec: Don't use %dir for paths that are fully included
    We were getting these messages from rpmbuild:
      warning: File listed twice: /usr/share/systemtap/runtime
      warning: File listed twice: /usr/share/systemtap/tapset
    Those two paths included entirely in systemtap-devel, so the %dir
    directive is redundant.  However, it should claim %{_datadir}/%{name}
    which those two are under.

commit 5ecd69990a5136be2082f54604b77275a87e39dd
Author: Josh Stone <>
Date:   Mon Aug 6 11:03:19 2012 -0700

    Add dyninst to systemtap.spec, for Fedora 18+ only


Summary of changes:
 systemtap.spec |   40 +++++++++++++++++++++++++++++++++++++---
 1 files changed, 37 insertions(+), 3 deletions(-)

systemtap: system-wide probe/trace tool

                 reply	other threads:[~2012-08-06 20:25 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).