public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: fche@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.2-345-g874e412
Date: Sat, 26 Jun 2010 00:29:00 -0000	[thread overview]
Message-ID: <20100626002942.15266.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  874e4125c9daf6dc5ed7c60bbed50e23af8affd1 (commit)
       via  bdb3681ae66405a30546d1c15bed4b74eb42f2c3 (commit)
       via  13c4a0b0a082c5ad9a756b1a67d56f93641a0969 (commit)
      from  b7410c21745912b77ef684916daae3791ba023ea (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 874e4125c9daf6dc5ed7c60bbed50e23af8affd1
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Jun 25 14:40:33 2010 -0400

    more deprecation policy elaboration

commit bdb3681ae66405a30546d1c15bed4b74eb42f2c3
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Jun 25 11:42:38 2010 -0400

    draft deprecation policy/mechanism

commit 13c4a0b0a082c5ad9a756b1a67d56f93641a0969
Author: Frank Ch. Eigler <fche@elastic.org>
Date:   Fri Jun 25 11:41:51 2010 -0400

    PR11343: document

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

Summary of changes:
 HACKING |   25 ++++++++++++++++++++++++-
 NEWS    |    5 +++++
 stap.1  |   37 ++++++++++++++++++++++++++++++++++++-
 3 files changed, 65 insertions(+), 2 deletions(-)


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


                 reply	other threads:[~2010-06-26  0:29 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=20100626002942.15266.qmail@sourceware.org \
    --to=fche@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).