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.6-586-g8c0bea1 Date: Mon, 12 Dec 2011 22:52:00 -0000 [thread overview] Message-ID: <20111212225246.15641.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 8c0bea1f29cdeb4fc7edf41f62333488cc3cf304 (commit) from be6b4e27c36f15a77fa51dd920a5b24f5e57cc89 (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 8c0bea1f29cdeb4fc7edf41f62333488cc3cf304 Author: Frank Ch. Eigler <fche@redhat.com> Date: Mon Dec 12 17:50:59 2011 -0500 configury: fix make -j all install Due to an autoconf weirdness, make -j all install would run make all-recursive and make install-recursive in parallel, and let the two builds step on each others' toes. * Makefile.am (install): Explicitly require all. Recurse by hand. * Makefile.in: Regenerated. ----------------------------------------------------------------------- Summary of changes: Makefile.am | 3 +++ Makefile.in | 5 +++-- 2 files changed, 6 insertions(+), 2 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2011-12-12 22:52 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=20111212225246.15641.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: 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).