public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: cmeek@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.7-269-g2398e3c
Date: Thu, 31 May 2012 18:25:00 -0000	[thread overview]
Message-ID: <20120531182512.6789.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  2398e3c6fd8ef2bb8695c2d108b724bbc0669370 (commit)
      from  5aa9ca38826e112308de1fe01931bdc53f0a1fc1 (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 2398e3c6fd8ef2bb8695c2d108b724bbc0669370
Author: Chris Meek <cmeek@redhat.com>
Date:   Thu May 31 14:19:04 2012 -0400

    PR13667: Hardcoded netfilter constants, cleaned up
    
    Since certain older versions of the kernel do not define some
    netfilter constants, we had to hardcode all the values
    so that it would compile on those older kernels (i.e. RHEL 4 and 5).
    This is OK, since we were only including the netfilter_* headers
    to map the constants to their equivalent values.

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

Summary of changes:
 tapset-netfilter.cxx |  180 +++++++++++++++++++++++---------------------------
 1 files changed, 82 insertions(+), 98 deletions(-)


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


                 reply	other threads:[~2012-05-31 18:25 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=20120531182512.6789.qmail@sourceware.org \
    --to=cmeek@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).