From: Eric Sandeen <sandeen@sandeen.net>
To: Dave Chinner <david@fromorbit.com>
Cc: Stefan Behrens <sbehrens@giantdisaster.de>, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfstests: before test execution, print test number to syslog
Date: Thu, 08 Mar 2012 16:29:05 -0600 [thread overview]
Message-ID: <4F5932B1.5040208@sandeen.net> (raw)
In-Reply-To: <20120305213512.GC3592@dastard>
On 3/5/12 3:35 PM, Dave Chinner wrote:
> On Mon, Mar 05, 2012 at 06:26:09PM +0100, Stefan Behrens wrote:
>> When the xfstests are executed in a batch (like "check 001-299")
>> and produce syslog output, it is helpful to know which test was
>> causing the output. Therefore each time a test is started, a
>> syslog message is generated that contains the number of the
>> xfstest.
>>
>> Signed-off-by: Stefan Behrens <sbehrens@giantdisaster.de>
>
> Looks ok.
>
> Reviewed-by: Dave Chinner <dchinner@redhat.com>
Thanks, I pushed this.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-03-08 22:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-05 17:26 [PATCH v2] xfstests: before test execution, print test number to syslog Stefan Behrens
2012-03-05 21:35 ` Dave Chinner
2012-03-08 22:29 ` 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=4F5932B1.5040208@sandeen.net \
--to=sandeen@sandeen.net \
--cc=david@fromorbit.com \
--cc=sbehrens@giantdisaster.de \
--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