From: Rich Johnston <rjohnston@sgi.com>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH V3] xfsdump: prevent segfault in cb_add_inogrp
Date: Mon, 21 Sep 2015 08:42:35 -0500 [thread overview]
Message-ID: <5600094B.3090206@sgi.com> (raw)
In-Reply-To: <55DE4492.90105@sgi.com>
On 08/26/2015 05:58 PM, Rich Johnston wrote:
> On 08/26/2015 05:56 PM, Dave Chinner wrote:
...
>> Can't believe I missed this first two times time through - the patch
>> is missing your signed-off-by. Just reply with it, and I'll fix it
>> up on commit. :)
> Dooh my bad
>
> Signed-off-by: Rich Johnston <rjohnston@sgi.com>
>>
>> Thanks, Rich!
>>
>> Cheers,
>>
>> Dave.
>>
>
Hey Dave,
Just curious when this patch are going to be committed?
Thanks
--Rich
These are also ready to go.
[PATCH V4] xfsrestore: fix fs uuid order check for incremental restores
http://oss.sgi.com/archives/xfs/2015-09/msg00185.html
[PATCH V2] xfsrestore: fix 2GB directory dump limitation for multi-stream
http://oss.sgi.com/archives/xfs/2015-09/msg00033.html
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-09-21 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-26 14:33 [PATCH] xfsdump: prevent segfault in cb_add_inogrp rjohnston
2015-08-26 16:42 ` Eric Sandeen
2015-08-26 17:10 ` Rich Johnston
2015-08-26 21:26 ` Dave Chinner
2015-08-26 17:36 ` [PATCH V2] " rjohnston
2015-08-26 21:37 ` Dave Chinner
2015-08-26 21:57 ` Rich Johnston
2015-08-26 22:19 ` Eric Sandeen
2015-08-26 22:27 ` Eric Sandeen
2015-08-26 22:21 ` Dave Chinner
2015-08-26 22:29 ` [PATCH V3] " rjohnston
2015-08-26 22:56 ` Dave Chinner
2015-08-26 22:58 ` Rich Johnston
2015-09-21 13:42 ` Rich Johnston [this message]
2015-08-26 23:00 ` Eric Sandeen
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=5600094B.3090206@sgi.com \
--to=rjohnston@sgi.com \
--cc=david@fromorbit.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