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: xfsprogs: update CHANGES file for release
Date: Wed, 30 Mar 2011 14:46:13 -0400	[thread overview]
Message-ID: <20110330184613.GA32141@infradead.org> (raw)
In-Reply-To: <1301507600.2953.13.camel@doink>

Note that you'll also need to update debian/changelog for the release,
just copy an old one that says upstream update and mention that it fixes
bug 618730.


> +	- Polish translation update

please credit this one to Jakub Bogusz

> +	- xfs_io now supports the "fpunch" command, as well as a
> +	  "-p" flag to the "fallocate command.  Both implement hole
> +	  punching.

please credit this Josef Bacik

> +	- A number of other bug fixes

please credit these to Ajeet Yadav and 

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

  reply	other threads:[~2011-03-30 18:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-30 17:53 xfsprogs: update CHANGES file for release Alex Elder
2011-03-30 18:46 ` Christoph Hellwig [this message]
2011-03-30 19:37 ` [PATCH v2] " Alex Elder
2011-03-30 21:40   ` 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=20110330184613.GA32141@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