From: Christoph Hellwig <hch@infradead.org>
To: Nathan Scott <nscott@aconex.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: update doc/CHANGES
Date: Sat, 24 Jan 2009 00:28:59 -0500 [thread overview]
Message-ID: <20090124052859.GA32606@infradead.org> (raw)
In-Reply-To: <1232774578.13684.5.camel@verge.scott.net.au>
On Sat, Jan 24, 2009 at 04:22:58PM +1100, Nathan Scott wrote:
> On Thu, 2009-01-22 at 19:56 -0500, Christoph Hellwig wrote:
> > Signed-off-by: Christoph Hellwig <hch@lst.de>
>
> > + - Various xfs_quta fixes, thanks to Arkadiusz Miskiewicz
>
> typo.
>
> > + - Addition of the xfs_fsr and xfs_estimate tools previous found
> > + in the xfsdump package
>
> rpm magic is probably needed in build/rpm/rpm.spec.in to prevent
> old versions of xfsdump from being installed alongside the new
> xfsprogs ... else rpm will report file conflicts, I think? Same
> will be needed in debian/control... hmm, both should be pretty
> easy - just change "Conflicts: xfsdump < 2.0.0" to "3.0.0" (and
> we should make xfsdump v3 at this time too, so its very clear).
Agreed. I think it's better to leave the debian part to you, and
I'll look into the rpm part later.
Any chance you could also review the fsr and estimate manpage
patches as they should go in before this one?
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-01-24 5:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-23 0:56 [PATCH] xfsprogs: update doc/CHANGES Christoph Hellwig
2009-01-24 5:22 ` Nathan Scott
2009-01-24 5:28 ` Christoph Hellwig [this message]
2009-01-24 5:52 ` Nathan Scott
2009-01-24 14:02 ` Christoph Hellwig
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=20090124052859.GA32606@infradead.org \
--to=hch@infradead.org \
--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