public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Chinner <david@fromorbit.com>
To: Rich Johnston <rjohnston@sgi.com>
Cc: Christoph Hellwig <hch@infradead.org>, xfs@oss.sgi.com
Subject: Re: [patch 1/1] xfsprogs: update version for 3.2.0-alpha2
Date: Tue, 19 Nov 2013 09:53:42 +1100	[thread overview]
Message-ID: <20131118225342.GX6188@dastard> (raw)
In-Reply-To: <528A3533.3080607@sgi.com>

On Mon, Nov 18, 2013 at 09:41:39AM -0600, Rich Johnston wrote:
> On 11/18/2013 09:11 AM, Christoph Hellwig wrote:
> >On Mon, Nov 18, 2013 at 09:03:13AM -0600, rjohnston@sgi.com wrote:
> >>+xfsprogs-3.2.0-alpha2 (18 November 2013)
> >>+	- Alpha release for the purpose of testing the CRC feature during the
> >>+	  v3.12 kernel -rc series.
> >
> >Please list the actual changes here, and also update the list for
> >-alpha1 which was missing all the usual information as well.
> >
> I will send a new V2 with the requested information after others
> have chimed in.
> 
> Attached are the commits so far:

I think what Christoph means is that there needs to be a summary of
all the changes made, not a list of the commits that were included.
i.e. a list of bugs fixed, features added and changes made written
in a way that a user would be able to look at and say "oh, they've
fixed the problem I saw"....

> commit 64eb960fb0d95bab9aa0c28f8c809bcaaeac564f
> Author: Eric Sandeen <sandeen@redhat.com>
> Date:   Thu Nov 14 20:54:02 2013 +0000
> 
>     xfsprogs: Fix stray semicolon in libxfs/rdwr.c

So something like that is not worth mentioning

> --
> commit 79e106f05f0fbffb89ab5401fb97af5391c6291f
> Author: Eric Sandeen <sandeen@redhat.com>
> Date:   Thu Nov 14 20:38:08 2013 +0000
> 
>     xfs_repair: correct docs for "-t" units

But this is as "fixed units in xfs_repair man page"

> --
> commit 1adfe5c6296d3ea6c182f31a6728fc94af9146f7
> Author: Eric Sandeen <sandeen@redhat.com>
> Date:   Fri Oct 18 22:30:18 2013 +0000
> 
>     xfs_fsr: fix SWAPEXT failures under selinux

That's worth mentioning

> --
> commit 275077754611e5a15672624e674265b54f1cb7ed
> Author: Eric Sandeen <sandeen@redhat.com>
> Date:   Fri Oct 18 22:09:07 2013 +0000
> 
>     xfs_fsr: extra debugging info

But this isn't.

> --
> commit 9b981421f503ba679097f8cd749af37cc42f5fd7
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Wed Nov 13 06:41:00 2013 +0000
> 
>     repair: fix leaf node directory data check

That isn't worth mentioning because it's a bug fix for a change in
this series....

> --
> commit 0cce4aa198f0470817bedb3781ea5b6955e43076
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Wed Nov 13 06:40:59 2013 +0000
> 
>     repair: Increase default repair parallelism on large filesystems
> --
> commit 61510437c627b529feb95ebffddd73df5ed5b104
> Author: Dave Chinner <dchinner@redhat.com>
> Date:   Wed Nov 13 06:40:58 2013 +0000
> 
>     repair: prefetching is turned off unnecessarily

But these are.

And so on - use your discretion...

Cheers,

Dave.
-- 
Dave Chinner
david@fromorbit.com

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

  reply	other threads:[~2013-11-18 22:53 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-18 15:03 [patch 1/1] xfsprogs: update version for 3.2.0-alpha2 rjohnston
2013-11-18 15:11 ` Christoph Hellwig
2013-11-18 15:41   ` Rich Johnston
2013-11-18 22:53     ` Dave Chinner [this message]
2013-11-19 17:01 ` [PATCH V2] " rjohnston
2013-11-19 17:21   ` Christoph Hellwig
2013-11-19 17:14 ` [PATCH V3] " rjohnston
2013-11-21  3:49   ` Eric Sandeen
2013-11-21  3:58     ` Rich Johnston
2013-11-21 16:27       ` Eric Sandeen
2013-11-22 18:37 ` [PATCH V4] " rjohnston
2013-11-22 19:04   ` Rich Johnston
2013-11-22 21:09   ` Eric Sandeen
2013-11-25 14:42     ` Rich Johnston
2013-11-25 14:54       ` Christoph Hellwig
2013-11-25 15:00   ` Rich Johnston

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=20131118225342.GX6188@dastard \
    --to=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=rjohnston@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