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-1.7-335-gb13c6a3
Date: Fri, 15 Jun 2012 21:17:00 -0000	[thread overview]
Message-ID: <20120615211709.24482.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  b13c6a37ed4a4f93943d942da75958e15b25c350 (commit)
      from  42da159946927cf0a89b0a970a5643bdb0edfcca (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 b13c6a37ed4a4f93943d942da75958e15b25c350
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jun 15 14:16:27 2012 -0700

    PR14168: Let stap_system() callers describe the command
    
    This fixes the gripe of commit 42da159, that error codes from
    "env ... make" were identified as env failures.
    
    * util.cxx (stap_system): Add a "description" parameter that names the
      command for the WARNING message.
    * util.h (stap_system): Keep the old form as a wrapper which uses
      args[0] as the description.
    * buildrun.cxx (run_make_cmd): Now more descriptive than ever before,
      pass the name "kbuild" to stap_system().

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

Summary of changes:
 buildrun.cxx |    2 +-
 util.cxx     |    6 +++---
 util.h       |    6 +++++-
 3 files changed, 9 insertions(+), 5 deletions(-)


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


                 reply	other threads:[~2012-06-15 21:17 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=20120615211709.24482.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).