From: Eric Sandeen <sandeen@redhat.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfstests: filter out latest xfsdump version messages
Date: Mon, 18 Jun 2012 11:48:37 -0500 [thread overview]
Message-ID: <4FDF5BE5.3000507@redhat.com> (raw)
In-Reply-To: <4FDF583A.2040403@redhat.com>
On 6/18/12 11:32 AM, Brian Foster wrote:
> On 06/18/2012 12:18 PM, Eric Sandeen wrote:
>> On 6/18/12 10:56 AM, Brian Foster wrote:
>>> The latest version of xfsdump/restore (3.1.0) causes dump tests
>>> to complain. Fix up the filter to include a wider selection of
>>> version numbers.
>>
>> Looks good to me, thanks - I'll merge it, but I think I'll
>> add a "^version" to it to make it a little more selective,
>> if that's ok with you.
>>
>
> Fine by me, thanks.
actually that's wrong, because it puts executable name at the beginning!
Sorry. I'll merge it as is, thanks.
-Eric
> Brian
>
>> Reviewed-by: Eric Sandeen <sandeen@redhat.com>
>>
>>> Signed-off-by: Brian Foster <bfoster@redhat.com>
>>> ---
>>> common.dump | 2 +-
>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/common.dump b/common.dump
>>> index ca09ec1..61d3f43 100644
>>> --- a/common.dump
>>> +++ b/common.dump
>>> @@ -863,7 +863,7 @@ _dump_filter_main()
>>> -e 's/1048576/BLOCKSZ/' \
>>> -e 's/2097152/BLOCKSZ/' \
>>> -e 's/(pid[ ]*[1-9][0-9]*)/\(pid PID\)/' \
>>> - -e '/version 3\.0/d' \
>>> + -e '/version [3-9]\.[0-9]/d' \
>>> -e 's/\/hw\/module.*$/SCRATCH_DEV/' \
>>> -e 's/xfsdump: ino map phase 1: .*/xfsdump: ino map <PHASES>/' \
>>> -e '/xfsdump: ino map phase [2]/,1d' \
>>
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-06-18 16:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-18 15:56 [PATCH] xfstests: filter out latest xfsdump version messages Brian Foster
2012-06-18 16:18 ` Eric Sandeen
2012-06-18 16:32 ` Brian Foster
2012-06-18 16:48 ` Eric Sandeen [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=4FDF5BE5.3000507@redhat.com \
--to=sandeen@redhat.com \
--cc=bfoster@redhat.com \
--cc=xfs@oss.sgi.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