From: Christoph Hellwig <hch@infradead.org>
To: Bill Kendall <wkendall@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [PATCH v2] xfsdump: use the full 32-bit generation number
Date: Mon, 13 Feb 2012 11:45:20 -0500 [thread overview]
Message-ID: <20120213164519.GA16732@infradead.org> (raw)
In-Reply-To: <4F393C08.6000801@sgi.com>
On Mon, Feb 13, 2012 at 10:36:24AM -0600, Bill Kendall wrote:
> On 02/12/2012 05:47 PM, Christoph Hellwig wrote:
> >Looks generally good to me, but is there any good reason to not make
> >the -K argument extensible by requiring a version argument, even if
> >that one currently only supports 2 and 3 as valid values?
>
> I thought about doing that, but given the low frequency of format
> changes decided it could wait until there's more than one old format
> to support. -K without an argument could be treated as "generate
> the previous media format", or with an argument it could generate
> a specific format. I'm okay with requiring a version argument though,
> being explicit is better.
>
> FWIW, the way things have always worked is that xfsrestore provides
> backwards compatibility for all dump formats. xfsdump has, until
> now, always generated the current format. It's nice to provide
> the ability to generate old formats during a transition period,
> but long-term I don't see xfsdump retaining support for generating
> all old formats.
Ok, sounds fine. I'll put it into the repository and after that we
should aim for an xfsdump 3.1.0 release ASAP.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-02-13 16:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-09 18:46 [PATCH v2] xfsdump: use the full 32-bit generation number Bill Kendall
2012-02-12 23:47 ` Christoph Hellwig
2012-02-13 16:36 ` Bill Kendall
2012-02-13 16: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=20120213164519.GA16732@infradead.org \
--to=hch@infradead.org \
--cc=wkendall@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.