From: Rich Johnston <rjohnston@sgi.com>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH V2] xfsrestore: fix fs uuid order check for incremental restores
Date: Thu, 3 Sep 2015 09:23:28 -0500 [thread overview]
Message-ID: <55E857E0.3010604@sgi.com> (raw)
In-Reply-To: <55E85407.7010106@sgi.com>
Please disregard, not what I meat to send.
--Rich
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-03 14:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 16:27 [PATCH] xfsrestore: fix fs uuid order check for incremental restores Rich Johnston
2015-08-26 21:31 ` Dave Chinner
2015-08-26 22:53 ` Rich Johnston
2015-09-01 19:36 ` Rich Johnston
2015-09-02 13:21 ` [RESEND PATCH] " Brian Foster
2015-09-02 18:49 ` Rich Johnston
2015-09-03 14:07 ` [PATCH V2] " Rich Johnston
2015-09-03 14:23 ` Rich Johnston [this message]
2015-09-03 23:43 ` [PATCH V3] " Rich Johnston
2015-09-08 12:47 ` Brian Foster
2015-09-11 17:01 ` Rich Johnston
2015-09-11 17:14 ` [PATCH V4] " Rich Johnston
2015-09-11 19:22 ` Brian Foster
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=55E857E0.3010604@sgi.com \
--to=rjohnston@sgi.com \
--cc=bfoster@redhat.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