From: Nathan Scott <nscott@aconex.com>
To: Iustin Pop <iusty@k1024.org>
Cc: David Chinner <dgc@sgi.com>, Ruben Porras <nahoo82@gmail.com>,
xfs@oss.sgi.com, cw@f00f.org
Subject: Re: XFS shrink functionality
Date: Wed, 06 Jun 2007 11:50:10 +1000 [thread overview]
Message-ID: <1181094610.3758.2.camel@edge.yarra.acx> (raw)
In-Reply-To: <20070605080012.GA10677@teal.hq.k1024.org>
On Tue, 2007-06-05 at 10:00 +0200, Iustin Pop wrote:
>
>
> So given these caveats, is there a chance that a) this will be
> actually
> useful and b) will this be accepted?
Theres no doubt that its useful, its probably the most frequently
requested feature for XFS from the community.
I'd imagine its acceptance will depend on code quality, testing,
etc, etc.
> The last time I tried to work on this there has been no real feedback
> and I'm thinking that maybe the code will be too intrusive and will
> give
> to little gain to be accepted.
IIRC, most people missed the patch last time cos it got bounced by the
list (cant remember why) - that was why I missed it for a long time,
anyway.
cheers.
--
Nathan
next prev parent reply other threads:[~2007-06-06 1:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 16:39 XFS shrink functionality Ruben Porras
2007-06-04 0:16 ` David Chinner
2007-06-04 8:41 ` Iustin Pop
2007-06-04 9:21 ` David Chinner
2007-06-05 8:00 ` Iustin Pop
2007-06-06 1:50 ` Nathan Scott [this message]
2007-06-07 8:18 ` David Chinner
2007-06-08 8:23 ` Ruben Porras
2007-06-08 10:15 ` Iustin Pop
2007-06-08 15:12 ` David Chinner
2007-06-08 16:03 ` Iustin Pop
2007-06-09 2:15 ` David Chinner
2007-06-08 19:47 ` Ruben Porras
2007-06-14 8:35 ` Ruben Porras
2007-06-14 9:14 ` David Chinner
2007-06-08 14:44 ` David Chinner
2007-06-19 22:22 ` XFS shrink (step 0) Ruben Porras
2007-06-19 23:42 ` David Chinner
2007-06-28 10:38 ` Ruben Porras
2007-06-29 6:55 ` David Chinner
2007-07-30 17:30 ` Ruben Porras
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=1181094610.3758.2.camel@edge.yarra.acx \
--to=nscott@aconex.com \
--cc=cw@f00f.org \
--cc=dgc@sgi.com \
--cc=iusty@k1024.org \
--cc=nahoo82@gmail.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