From: Eric Sandeen <sandeen@sandeen.net>
To: Niv Sardi <xaiki@sgi.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: small problem w/ new xfs defaults patch
Date: Sun, 20 Jan 2008 23:29:25 -0600 [thread overview]
Message-ID: <47942DB5.6040708@sandeen.net> (raw)
In-Reply-To: <20080121051341.GA31708862@melbourne.sgi.com>
Niv Sardi wrote:
> * Eric Sandeen <sandeen@sandeen.net> [2008-01-20 21:46:39 -0600]:
>
>> Index: xfsprogs-2.9.4/growfs/xfs_growfs.c
>> ===================================================================
> [...]
>> couple things... you lost a "\n" off the end of the data section there...
>
> That has been fixed, I guess it needs to be sent to oss (barry?)
Ok, see that. Sorry... grabbed the original patch and didn't check cvs
for updates.
Thanks,
-Eric
>> Also, do you really want to drop reporting of unwritten extents? Even
>> if you're disallowing the selection on new mkfs's there may still be
>> different flavors of filesystems in existence, should it still be reported?
>
> I don't really care, whatever the oss/xfs-master people like best.
>
> Cheers
next prev parent reply other threads:[~2008-01-21 5:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-21 3:46 small problem w/ new xfs defaults patch Eric Sandeen
2008-01-21 5:13 ` Niv Sardi
2008-01-21 5:29 ` Eric Sandeen [this message]
2008-01-22 2:28 ` Timothy Shimmin
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=47942DB5.6040708@sandeen.net \
--to=sandeen@sandeen.net \
--cc=xaiki@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