public inbox for systemtap@sourceware.org
 help / color / mirror / Atom feed
From: William Cohen <wcohen@redhat.com>
To: Tom Zanussi <zanussi@us.ibm.com>
Cc: systemtap@sources.redhat.com
Subject: Re: proposed relayfs changes and systemtap
Date: Thu, 16 Mar 2006 15:39:00 -0000	[thread overview]
Message-ID: <441986BB.8010700@redhat.com> (raw)
In-Reply-To: <17433.33449.763501.889188@tut.ibm.com>

Tom Zanussi wrote:
> William Cohen writes:
>  > Tom Zanussi wrote:
>  > > Tom Zanussi writes:
>  > >  > Hi,
>  > >  > 
>  > >  > Someone over the weekend posted a patch to remove the filesystem part
>  > >  > of relayfs and instead have applications' relayfs files live in other
>  > >  > filesytems instead:
>  > >  > 
>  > >  > http://marc.theaimsgroup.com/?l=linux-kernel&m=114036950922176&w=2
>  > > 
>  > > Actually, this is probably a better link to the patches and thread:
>  > > 
>  > > http://marc.theaimsgroup.com/?l=linux-kernel&m=114038358624583&w=2
>  > > 
>  > > Tom
>  > > 
>  > > 
>  > 
>  > Hi Tom,
>  > 
>  > The nightly tests buildok and pass-5 tests failed due to the following 
>  > checkin:
>  > 
>  > 2006-03-15 Tom Zanussi  <zanussi@us.ibm.com>
>  > 
>  >          * configure.ac: Add check for relayfs version.
>  >          * configure: Regenerated.
>  >          * stp_check.in: Remove bundled relayfs loading/compilation, add
>  >          check for relay (vs relayfs).
>  > 
>  > The parser tests won't find relayfs-config.h nor will the pass-5 tests 
>  > find the include file.
> 
> Hi,
> 
> I just checked in new changes for that - can you get the latest from
> cvs and try again?  Sorry for the inconvenience.
> 
> Tom

That fixed the problem. The tests seem to run much better now.

-Will

      reply	other threads:[~2006-03-16 15:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-21 14:57 Tom Zanussi
2006-02-21 15:06 ` Tom Zanussi
2006-03-16 15:16   ` William Cohen
2006-03-16 15:22     ` Tom Zanussi
2006-03-16 15:39       ` William Cohen [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=441986BB.8010700@redhat.com \
    --to=wcohen@redhat.com \
    --cc=systemtap@sources.redhat.com \
    --cc=zanussi@us.ibm.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).