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-130-gcab11fd Date: Thu, 02 Aug 2012 18:04:00 -0000 [thread overview] Message-ID: <20120802180427.31122.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 cab11fd17e760cfe8599d765d640eeefca17d9e3 (commit) from b2103a16391bd00c9d891d61249a93a95a711584 (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 cab11fd17e760cfe8599d765d640eeefca17d9e3 Author: Josh Stone <jistone@redhat.com> Date: Thu Aug 2 10:55:57 2012 -0700 stapdyn & staprun: Use the top-level git_version.h Yo dawg, I herd you like Makefile recursion, so I put some recursion in your recursion so you can version while you version. Less duplication + more recursion == win? Another option is to flatten stapdyn and staprun Makefiles altogether into the root Makefile, but for now, this is less invasive. Changing the includes to ../git_version.h is not strictly necessary, since we also have "-I..", but this way developers won't get burned by old git_version.h files sitting in staprun/ or stapdyn/. ----------------------------------------------------------------------- Summary of changes: stapdyn/Makefile.am | 33 +++------------------------------ stapdyn/Makefile.in | 33 +++------------------------------ stapdyn/stapdyn.cxx | 2 +- staprun/Makefile.am | 32 +++----------------------------- staprun/Makefile.in | 34 +++++----------------------------- staprun/common.c | 2 +- 6 files changed, 16 insertions(+), 120 deletions(-) hooks/post-receive -- systemtap: system-wide probe/trace tool
reply other threads:[~2012-08-02 18: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=20120802180427.31122.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).