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.7-132-gca73974
Date: Thu, 22 Mar 2012 14:54:00 -0000	[thread overview]
Message-ID: <20120322145421.22393.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  ca73974d84f94065dbabce2a2044d17a83bade57 (commit)
       via  8b4d227971f74e7aa49f2019033888537656f22a (commit)
      from  2a885a4a9ca1826187c97c7eb128b06b4a5222f2 (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 ca73974d84f94065dbabce2a2044d17a83bade57
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Mar 22 15:16:22 2012 +0100

    proc_mem.stp: Use PF_STARTING conditionally.
    
    Use the PF_STARTING flag only conditionally on it being defined.
    Kernel commit v3.3-rc6-27-g6e27f63 - vfork: kill PF_STARTING, removed it.

commit 8b4d227971f74e7aa49f2019033888537656f22a
Author: Mark Wielaard <mjw@redhat.com>
Date:   Thu Mar 22 15:01:04 2012 +0100

    debugtypes.exp: Remove verbose debug output.

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

Summary of changes:
 tapset/proc_mem.stp                        |   10 +++++++++-
 testsuite/systemtap.pass1-4/debugtypes.exp |    2 --
 2 files changed, 9 insertions(+), 3 deletions(-)


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


                 reply	other threads:[~2012-03-22 14:54 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=20120322145421.22393.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).