From: Eric Sandeen <sandeen@sandeen.net>
To: Eric Sandeen <sandeen@redhat.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH 0/2] xfs_logprint: 2 fixes
Date: Thu, 01 Nov 2012 11:33:14 -0500 [thread overview]
Message-ID: <5092A44A.9010204@sandeen.net> (raw)
In-Reply-To: <5092A1DE.10609@redhat.com>
On 11/1/12 11:22 AM, Eric Sandeen wrote:
> I've run into a couple bugs running logprint, 2 patches follow to try to fix them up.
>
> -Eric
Sigh, fix subject. xfsdump on the brain, still.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2012-11-01 16:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-01 16:22 [PATCH 0/2] xfsdump: 2 fixes Eric Sandeen
2012-11-01 16:26 ` [PATCH 1/2] xfsdump: Handle multiply-logged inode fields Eric Sandeen
2012-11-01 16:33 ` [PATCH 1/2 V2] xfs_logprint: " Eric Sandeen
2012-11-02 13:01 ` Christoph Hellwig
2012-11-02 14:39 ` Eric Sandeen
[not found] ` <20130122175530.GR27055@sgi.com>
[not found] ` <20130122210511.GK2498@dastard>
2013-01-28 20:47 ` Eric Sandeen
2013-01-28 21:31 ` Ben Myers
2012-11-01 16:32 ` [PATCH 2/2] xfs_logprint: Handle continued inode transactions Eric Sandeen
2012-11-02 13:04 ` Christoph Hellwig
2012-11-02 14:35 ` Eric Sandeen
2012-11-01 16:33 ` Eric Sandeen [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=5092A44A.9010204@sandeen.net \
--to=sandeen@sandeen.net \
--cc=sandeen@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