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. rhel52-ga-447-gcfa2ca3
Date: Fri, 27 Jun 2008 23:22:00 -0000	[thread overview]
Message-ID: <20080627232229.19266.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  cfa2ca3cbf2da7bbabcdf35c3085a969bd2370e4 (commit)
      from  5e86a4eef7e29d89849d522bcdbe96e7a1e4b6b8 (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 cfa2ca3cbf2da7bbabcdf35c3085a969bd2370e4
Author: Josh Stone <joshua.i.stone@intel.com>
Date:   Fri Jun 27 16:19:19 2008 -0700

    Always include libdw using link groups.
    
    This is necessary for distros that ship static libdw, Roland suggested
    that it shouldn't hurt to do it this way on other distros too.  It's
    nicer now not to require the extra "--enable-staticdw" configure flag.

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

Summary of changes:
 configure    |  256 +---------------------------------------------------------
 configure.ac |   29 +------
 2 files changed, 7 insertions(+), 278 deletions(-)


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


                 reply	other threads:[~2008-06-27 23:22 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=20080627232229.19266.qmail@sourceware.org \
    --to=jistone@sourceware.org \
    --cc=systemtap-cvs@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).