From: Christoph Hellwig <hch@infradead.org>
To: bpm@sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
Nathan Scott <nathans@debian.org>,
xfs@oss.sgi.com
Subject: Re: [patch 1/1] xfsdump: update summaries in preparation for release
Date: Mon, 19 Mar 2012 18:31:11 -0400 [thread overview]
Message-ID: <20120319223111.GA28162@infradead.org> (raw)
In-Reply-To: <20120319204350.149959363@sgi.com>
Looks good, but I'd bump the version to 3.1.1, mostly due to the
multistream support that requires pthreads now.
Reviewed-by: Christoph Hellwig <hch@lst.de>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-03-19 22:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-19 20:42 [patch 0/1] xfsdump: update summaries for 3.0.7 release bpm
2012-03-19 20:42 ` [patch 1/1] xfsdump: update summaries in preparation for release bpm
2012-03-19 22:31 ` Christoph Hellwig [this message]
2012-03-20 18:18 ` Ben Myers
-- strict thread matches above, loose matches on Subject: below --
2012-03-20 20:43 [patch 0/1] xfsdump: update summaries for 3.1.0 release bpm
2012-03-20 20:43 ` [patch 1/1] xfsdump: update summaries in preparation for release bpm
2012-03-21 18:02 ` Christoph Hellwig
2012-03-21 18:57 ` Nathan Scott
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=20120319223111.GA28162@infradead.org \
--to=hch@infradead.org \
--cc=bpm@sgi.com \
--cc=nathans@debian.org \
--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