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.6-234-ge13b5ab
Date: Tue, 20 Sep 2011 10:00:00 -0000	[thread overview]
Message-ID: <20110920095959.14158.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  e13b5aba4d5fc678d58556b3e3faf74fea94eb47 (commit)
      from  6c40239db2042808a2ba6af56186a82291267cf2 (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 e13b5aba4d5fc678d58556b3e3faf74fea94eb47
Author: Mark Wielaard <mjw@redhat.com>
Date:   Tue Sep 20 11:48:28 2011 +0200

    Introduce _stp_get_uregs and _STP_PROBE_STATE_FULL_UREGS flag.
    
    No actual functionality change yet. _STP_PROBE_STATE_FULL_UREGS
    is set for context probe_flags if full user register set is available
    after calling _stp_get_uregs().

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

Summary of changes:
 runtime/runtime_defines.h |    2 ++
 runtime/stack.c           |   31 +++++++++++++++++++++++--------
 2 files changed, 25 insertions(+), 8 deletions(-)


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


                 reply	other threads:[~2011-09-20 10:00 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=20110920095959.14158.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).