public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mark Goodwin <markgw@sgi.com>
Cc: xfs-dev <xfs-dev@sgi.com>, xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump support for 64K page size
Date: Thu, 8 Jan 2009 10:37:08 -0500	[thread overview]
Message-ID: <20090108153708.GA30563@infradead.org> (raw)
In-Reply-To: <4965629C.2000703@sgi.com>

On Thu, Jan 08, 2009 at 01:19:08PM +1100, Mark Goodwin wrote:
> 
> 
> Bill Kendall wrote:
> > Various fixes to allow xfsdump/xfsrestore to work with 64K
> > page size. This is essentially Chinner's patch from a while
> > back.
> >
> > Signed-off-by: Bill Kendall <wkendall@sgi.com>
> 
> Lachlan reviewed and ack'd this on an internal list and I've committed
> it (on Bill's behalf) as follows :
> 
> git://oss.sgi.com/xfs/cmds/xfsdump.git
> 	commit 9502587dbbfdd465958889a568dc2842f10b1ff9
> 	Author: Mark Goodwin <markgw@sgi.com>
> 	Date:   Thu Jan 8 12:37:53 2009 +1100
> 
> 	    Various fixes to allow xfsdump/xfsrestore to work with 64K
> 	    page size. This is essentially Chinner's patch from a while
> 	    back.
> 	
> 	    Signed-off-by: Bill Kendall <wkendall@sgi.com>
> 	    Signed-off-by: Lachlan McIlroy <lachlan@sgi.com>
> 	    Signed-off-by: Mark Goodwin <markgw@sgi.com>
> 
> and for the libhandle changes :

If you commit something on someone else's behalf please use the --author
argument to git-commit so that it shows up as coming from that author
in the git version history.  Or just use git-am on the patch mail which
will sort out all this by itself.

> This introduces a dependency between xfsdump and libhandle (in xfsprogs),
> which may or may not be an issue now that the cmds are in split trees.

It's not a new depdency.  xfsdump depended on libhandle for a long time
(and before it did depend on dmapi IIRC).  Just to actually get dump
properly working with 64k pages you need the most uptodate version
of both packages.

> I guess maybe xfsdump/restore should rightfully be part of xfsprogs?

I think having them split makes a lot of sense as many people don't
need dump.  What we should eventually do is to move xfs_fsr over to
xfsprogs.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2009-01-08 15:37 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-07 15:10 [PATCH] xfsdump support for 64K page size Bill Kendall
2009-01-08  2:19 ` Mark Goodwin
2009-01-08 15:37   ` Christoph Hellwig [this message]
2009-01-08 22:28   ` Dave Chinner
2009-01-08 23:02     ` Eric Sandeen
2009-01-09 19:36     ` Bill Kendall
2009-01-09 19:41       ` Christoph Hellwig
2009-01-14 22:48       ` Dave Chinner
2009-01-15 18:59         ` Bill Kendall

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=20090108153708.GA30563@infradead.org \
    --to=hch@infradead.org \
    --cc=markgw@sgi.com \
    --cc=xfs-dev@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