From: Christoph Hellwig <hch@infradead.org>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: add xfs_estimate manpage
Date: Mon, 26 Jan 2009 02:45:47 -0500 [thread overview]
Message-ID: <20090126074547.GA27188@infradead.org> (raw)
In-Reply-To: <497C7718.5090607@sandeen.net>
On Sun, Jan 25, 2009 at 08:28:40AM -0600, Eric Sandeen wrote:
> Christoph Hellwig wrote:
> > xfs_Estimate has been moved to xfsprogs a while ago, so the manpage
> > should follow it.
>
> Hmm we need a patch to remove from dump too right :)
I already put that in.
> ACK for the move part, but some update to the man page to give a hint as
> to why this tool is useful seems reasonable... why would I want to use
> this thing?
>
> Also as an aside, why does the log size matter for space ultimately used?
I have no idea what this tools is useful for. It always seemed rather odd
to me.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-01-26 7:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:45 [PATCH] xfsprogs: add xfs_estimate manpage Christoph Hellwig
2009-01-25 14:28 ` Eric Sandeen
2009-01-26 7:45 ` Christoph Hellwig [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=20090126074547.GA27188@infradead.org \
--to=hch@infradead.org \
--cc=sandeen@sandeen.net \
--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