public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: Josh Stone <jistone@redhat.com>
To: Wade Farnsworth <wade_farnsworth@mentor.com>
Cc: systemtap@sourceware.org, fche@redhat.com
Subject: Re: [PATCH v4 0/3] Introduce stap options --sysroot and --sysenv
Date: Fri, 09 Mar 2012 06:56:00 -0000	[thread overview]
Message-ID: <4F59A977.9050206@redhat.com> (raw)
In-Reply-To: <4F58C6B0.6020707@mentor.com>

On 03/08/2012 06:48 AM, Wade Farnsworth wrote:
> This patchset introduces --sysroot and --sysenv options for stap, which
> improve functionality in environments where the compiling system differs
> from the one running the probes.
> 
> See Patch 1/3's description for more details on what has been implemented.
> 
> v2 - Implemented several improvements per Josh Stone's comments.
> v3 - Further improvements per Josh Stone.  Include documentation and test cases
>      for the new options.
> v4 - Add more detail to the man page for --sysroot to clarify which paths
>      are affected.
>    - Changed handling of paths where both sysroot and non-
>      sysroot versions are needed so that it's clear which version we're tracking.
>    - Store the sysenv variable as map<string, string> instead of
>      <string, char*>.
>     
> 
> Wade Farnsworth (3):
>   PR12331: Introduce stap options --sysroot and --sysenv
>   PR12331: Document --sysroot and --sysenv
>   PR12331: Add testcase for --sysroot and --sysenv

Thanks, these are now merged and pushed.  I did have to fix some
conflicts with commit 372c6458, but I think I did that right. :)

Josh

      parent reply	other threads:[~2012-03-09  6:56 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-09 14:51 [PATCH] Add --sysroot option Wade Farnsworth
2012-01-20 15:49 ` Wade Farnsworth
2012-01-20 18:11 ` Josh Stone
2012-02-09 18:26 ` [PATCH v2] PR12331: Introduce stap options --sysroot and --sysenv Wade Farnsworth
2012-02-17 14:39   ` Wade Farnsworth
2012-02-24 22:56   ` Josh Stone
2012-03-02 14:47   ` [PATCH v3 0/3] " Wade Farnsworth
2012-03-02 14:48     ` [PATCH v3 1/3] " Wade Farnsworth
2012-03-02 14:48     ` [PATCH v3 2/3] PR12331: Document " Wade Farnsworth
2012-03-02 14:49     ` [PATCH v3 3/3] PR12331: Add testcase for " Wade Farnsworth
2012-03-08 14:48     ` [PATCH v4 0/3] Introduce stap options " Wade Farnsworth
2012-03-08 14:49       ` [PATCH v4 1/3] PR12331: " Wade Farnsworth
2012-03-08 14:50       ` [PATCH v4 2/3] PR12331: Document " Wade Farnsworth
2012-03-08 14:51       ` [PATCH v4 3/3] PR12331: Add testcase for " Wade Farnsworth
2012-03-09  6:56       ` Josh Stone [this message]

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=4F59A977.9050206@redhat.com \
    --to=jistone@redhat.com \
    --cc=fche@redhat.com \
    --cc=systemtap@sourceware.org \
    --cc=wade_farnsworth@mentor.com \
    /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).