From: Niv Sardi <xaiki@sgi.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Niv Sardi-Altivanik <xaiki@sgi.com>,
sgi.bugs.xfs@engr.sgi.com, xfs@oss.sgi.com,
Lachlan McIlroy <lachlan@sgi.com>
Subject: Re: TAKE 977771 -
Date: Fri, 29 Feb 2008 11:47:05 +1100 [thread overview]
Message-ID: <ncchcfsk2ra.fsf@sgi.com> (raw)
In-Reply-To: <47C72FC5.7030908@sandeen.net> (Eric Sandeen's message of "Thu, 28 Feb 2008 16:03:49 -0600")
Eric Sandeen <sandeen@sandeen.net> writes:
> Niv Sardi-Altivanik wrote:
>> If you mount an XFS filesystem with no mount options at all, then
>> the "ikeep" option is set rather than "noikeep".
>
> Thanks for getting this in.
>
> 2 questions...
>
> Is it going to make 2.6.25?
I hope so, but as I've been told to stay away from git trees it's in
lachlan's (over-busy) hands.
> And can you add a little text description to your subject line, for
> those doing inbox searches for things? :)
Yep, sorry, I thought our tools were not that d^W^W^Wsmarter than they
are.
Cheers,
--
Niv Sardi
prev parent reply other threads:[~2008-02-29 0:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-28 0:32 TAKE 977771 - Niv Sardi-Altivanik
2008-02-28 22:03 ` Eric Sandeen
2008-02-29 0:47 ` Niv Sardi [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=ncchcfsk2ra.fsf@sgi.com \
--to=xaiki@sgi.com \
--cc=lachlan@sgi.com \
--cc=sandeen@sandeen.net \
--cc=sgi.bugs.xfs@engr.sgi.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