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.8-44-gd9b0c1c Date: Thu, 19 Jul 2012 03:04:00 -0000 [thread overview] Message-ID: <20120719030436.8344.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 d9b0c1c8712ff255d4b6171fdb0e1ec39f444501 (commit) from 73d53dd2213ce54a72db9b3bd029eb1f39760656 (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 d9b0c1c8712ff255d4b6171fdb0e1ec39f444501 Author: Josh Stone <jistone@redhat.com> Date: Wed Jul 18 18:33:12 2012 -0700 Further tweak to glibc/kernel-headers workaround ... following commit 037853b4644bb6ebd68e2f1fac11c3636f551d8e, for https://bugzilla.redhat.com/show_bug.cgi?id=840902 Seems it's not always possible to avoid linux/types.h for the conflict it presents with sys/select.h. Now include linux/types.h very early, so glibc can stomp over it with #undef and #define, rather than vice versa. ----------------------------------------------------------------------- Summary of changes: staprun/staprun.h | 5 +++++ 1 files changed, 5 insertions(+), 0 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-07-19 3:04 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=20120719030436.8344.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: linkBe 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).