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-22-gf747017
Date: Sat, 22 Jan 2011 00:05:00 -0000	[thread overview]
Message-ID: <20110122000547.8513.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  f7470174cbaa50758a38c8cb9f5c13847b17254e (commit)
       via  6afaa1cbfcd56f4fa4e4ab47248d889ccf4dedf9 (commit)
       via  91fa953dfd30090b279e23be156af229e2b422e6 (commit)
      from  a0e2728a26d3ff39ac5cea3758fcbe18951451bc (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 f7470174cbaa50758a38c8cb9f5c13847b17254e
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jan 21 15:44:41 2011 -0800

    Audit some minus/dash/hyphen use in manpages
    
    Groff treats "-" as a hyphen, U+2010.  When the intention is to produce
    a literal ASCII minus sign, U+002D, it must be "\-".  This matters for
    command-line options and examples to be copyable from the manpage.
    
    I've updated cases that should obviously be escaped.  At a glance, I
    think we have other cases that could be normal hyphens, not escaped, but
    that's less of an issue.

commit 6afaa1cbfcd56f4fa4e4ab47248d889ccf4dedf9
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jan 21 15:25:35 2011 -0800

    Add the cache options from commit d105f66 to stap.1

commit 91fa953dfd30090b279e23be156af229e2b422e6
Author: Josh Stone <jistone@redhat.com>
Date:   Fri Jan 21 14:06:52 2011 -0800

    Add support for real URI syntax in remote targets
    
    We still only support SSH for now, but this opens the door for other
    protocols.  All of the following should work:
    
      --remote host
      --remote user@host
      --remote ssh://host/
      --remote ssh://user@host/
    
    URI paths, queries, and fragments are all parsed, but don't have any
    meaning yet, so they're treated as an error.  I can imagine using this
    for protocol-specific options though, e.g. ssh://host/?Compression=yes
    
    * remote.cxx (class uri_decoder): New, breaks down a URI string.
      (ssh_remote::ssh_remote): Add a constructor using a uri_decoder.
      (remote::create): Redirect based on the scheme of URI-looking remote
      targets.  Assume all others are still plain [user@]host for ssh.

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

Summary of changes:
 dtrace.1                  |   10 ++--
 man/tapset::snmp.3stap    |    2 +-
 remote.cxx                |  110 ++++++++++++++++++++++++++++++++++++++-------
 runtime/staprun/staprun.8 |   12 +++---
 stap-merge.1              |   20 ++++----
 stap-server.8.in          |   14 +++---
 stap.1                    |   69 ++++++++++++++++++----------
 stappaths.7.in            |   24 +++++-----
 stapprobes.3stap          |    8 ++--
 stapvars.3stap            |    4 +-
 10 files changed, 184 insertions(+), 89 deletions(-)


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


                 reply	other threads:[~2011-01-22  0:05 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=20110122000547.8513.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).