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.4-146-ge3d0ec4
Date: Fri, 11 Mar 2011 02:54:00 -0000	[thread overview]
Message-ID: <20110311025432.26818.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  e3d0ec492a0495509e7a93351b4a3b42e83a04fc (commit)
      from  f7e13eadc3f666fd356ca7cdb42f1de8d53b5e4b (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 e3d0ec492a0495509e7a93351b4a3b42e83a04fc
Author: Josh Stone <jistone@redhat.com>
Date:   Thu Mar 10 18:45:35 2011 -0800

    Build -u and uprobes_path in a single argument
    
    Optional arguments in getopt have to be part of the same word, so this
    lets staprun read the uprobes_path correctly.  This was a regression
    from the change to vectorized commands.
    
    * buildrun.cxx (make_run_command): Append uprobes_path to -u.

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

Summary of changes:
 buildrun.cxx |    2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2011-03-11  2: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=20110311025432.26818.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).