public inbox for systemtap-cvs@sourceware.org
help / color / mirror / Atom feed
From: mark@sourceware.org
To: systemtap-cvs@sourceware.org
Subject: [SCM] systemtap: system-wide probe/trace tool branch, master, updated. release-1.6-395-gc030492
Date: Wed, 09 Nov 2011 16:09:00 -0000	[thread overview]
Message-ID: <20111109160954.24125.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  c0304922051faad1ebc38cd87e6b58f676294cd6 (commit)
      from  d6f447636c8f43e354b5cbf9a7d84bd867a08211 (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 c0304922051faad1ebc38cd87e6b58f676294cd6
Author: Mark Wielaard <mjw@redhat.com>
Date:   Wed Nov 9 17:06:28 2011 +0100

    testsuite/systemtap.base/plt.c: define _GNU_SOURCE for stpcpy.
    
    stpcpy is strange. On some older systems it is only declared when
    _GNU_SOURCE is defined. The STPCPY(3) manpage says:
    
       This function is not part of the C or POSIX.1  standards,  and  is  not
       customary  on Unix systems, but is not a GNU invention either.  Perhaps
       it comes from MS-DOS.

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

Summary of changes:
 testsuite/systemtap.base/plt.c |    3 ++-
 1 files changed, 2 insertions(+), 1 deletions(-)


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


                 reply	other threads:[~2011-11-09 16:09 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=20111109160954.24125.qmail@sourceware.org \
    --to=mark@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).