public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: bpm@sgi.com
To: xfs@oss.sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	Nathan Scott <nathans@debian.org>,
	bpm@sgi.com
Subject: [patch 0/1] xfsdump: update summaries for 3.1.0 release
Date: Tue, 20 Mar 2012 15:43:16 -0500	[thread overview]
Message-ID: <20120320204316.811460772@sgi.com> (raw)

Hi,

	Here is an updated draft of the summaries for the upcoming xfsdump
	release.  Christoph suggested releasing to version 3.1.0... and I think
	that this seems reasonable given the multithreaded dump/restore feature
	from Bill.  I also added summaries for a few items I missed last time.

	Please take a look.

Thanks,
	Ben

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

             reply	other threads:[~2012-03-21 17:28 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 20:43 bpm [this message]
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=20120320204316.811460772@sgi.com \
    --to=bpm@sgi.com \
    --cc=hch@infradead.org \
    --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