public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsdump: update summaries in preparation for release 3.0.6
Date: Mon, 10 Oct 2011 12:34:23 -0400	[thread overview]
Message-ID: <20111010163423.GD11902@infradead.org> (raw)
In-Reply-To: <201110052210.p95MAXGI012463@stout.americas.sgi.com>

On Wed, Oct 05, 2011 at 05:10:33PM -0500, Alex Elder wrote:
> The following is a draft of summaries to be included in the next
> release of xfsdump.

The content looks good, but it's fairly different and much more verbose
style than we traditionally did, which also generally focussed on user
visible changes.

This is how I would have written the log in the "old" style:

xfsdump-3.0.6 (5 October 2011)
	- unconditionally add checksums to various dump headers in
	  xfsdump.
	- verify checksums if present in xfsrestore.
	- use the POSIX signal API instead of the legacy SysV API.
	- various internal cleanups and refactoring in xfsdump and
	  xfsrestore.
	- lift the limit of options in dialogs from 8 to 99.
	- various build system fixes, thanks to Ted Ts'o.

same applies to the other logs.

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

  parent reply	other threads:[~2011-10-10 16:34 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-05 22:10 [PATCH] xfsdump: update summaries in preparation for release 3.0.6 Alex Elder
2011-10-05 22:34 ` Bill Kendall
2011-10-10 16:34 ` Christoph Hellwig [this message]
2011-10-13 10:43   ` Alex Elder

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=20111010163423.GD11902@infradead.org \
    --to=hch@infradead.org \
    --cc=aelder@sgi.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