From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfsprogs: add missing CHANGES entry
Date: Wed, 07 Oct 2009 17:02:59 -0500 [thread overview]
Message-ID: <4ACD1013.6000502@sandeen.net> (raw)
In-Reply-To: <20091006151102.GA30964@infradead.org>
Christoph Hellwig wrote:
> The 3.0.4 release for debian actually had a few more changes than documented.
> Add the missing entries so that they appear in the right spot for future
> releases.
>
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
looks fine to me,
Reviewed-by: Eric Sandeen <sandeen@sandeen.net>
> Index: xfsprogs-dev/doc/CHANGES
> ===================================================================
> --- xfsprogs-dev.orig/doc/CHANGES 2009-10-06 10:51:31.609004058 -0300
> +++ xfsprogs-dev/doc/CHANGES 2009-10-06 10:54:13.695006442 -0300
> @@ -1,4 +1,10 @@
> xfsprogs-3.0.4 (17 September 2009)
> + - Fix a memory leak in xfsprogs.
> + - Increase hash chain length in xfsprogs when running out of memory.
> + - Fix dmsetup invocation in libdisk to avoid warnings during mkfs
> + on multipath devices.
> + - Fix the -V option to various installed tools.
> + - Small internal fixes to please the clang semantical analysis tool.
> - Debian packaging updates.
> - Rework Makepkgs and Makefiles to improve deb generation.
>
>
> _______________________________________________
> xfs mailing list
> xfs@oss.sgi.com
> http://oss.sgi.com/mailman/listinfo/xfs
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-10-07 22:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 15:11 [PATCH] xfsprogs: add missing CHANGES entry Christoph Hellwig
2009-10-07 22:02 ` 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=4ACD1013.6000502@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.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