From: Eric Sandeen <sandeen@sandeen.net>
To: Nathan Scott <nscott@aconex.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH, RFC] put xfs build features into the stats file
Date: Sun, 19 Apr 2009 22:00:58 -0500 [thread overview]
Message-ID: <49EBE56A.1070906@sandeen.net> (raw)
In-Reply-To: <1520890652.3597921240196368192.JavaMail.root@mail-au.aconex.com>
Nathan Scott wrote:
> Separate file? That line uses a comma separator ... differs to
> every other line in that stats file, painful for parsers. And
> no risk of breaking anything if its a separate file.
>
> cheers.
Hm good point. Might do; not that big a deal, just wanted to be able to
gracefully skip acl/attr xfstests if the xfs build didn't support it :)
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-04-20 3:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-20 2:34 [PATCH, RFC] put xfs build features into the stats file Eric Sandeen
2009-04-20 2:59 ` Nathan Scott
2009-04-20 3:00 ` Eric Sandeen [this message]
2009-04-21 14:15 ` Christoph Hellwig
2009-04-21 15:20 ` Eric Sandeen
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=49EBE56A.1070906@sandeen.net \
--to=sandeen@sandeen.net \
--cc=nscott@aconex.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