From: Alex Elder <aelder@sgi.com>
To: Nathan Scott <nathans@aconex.com>
Cc: xfs <xfs@oss.sgi.com>
Subject: Re: Review: xfsprogs with libblkid enabled for Debian
Date: Mon, 30 Aug 2010 09:21:37 -0500 [thread overview]
Message-ID: <1283178097.5273.97.camel@doink> (raw)
In-Reply-To: <239606566.371721282829201737.JavaMail.root@mail-au.aconex.com>
On Thu, 2010-08-26 at 23:26 +1000, Nathan Scott wrote:
> ----- "Christoph Hellwig" <hch@infradead.org> wrote:
>
> > I'm fine with pushing out a new 3.1.3 release as it's time anyway,
> > but
> > can we also include Dave's patch to add XFS_IOC_ZERO_RANGE support to
> > xfs_io and the xfsctl manpage first?
> >
> > Next week also has Alex back from vacation, so I'd suggest waiting if
> > he has any input on this.
>
> As discussed on IRC, I made the changes and push out a new release.sh
> tagged git update to kernel.org. I pushed the src tarball to oss also,
> and libblkid enabled packages will be uploaded to Debian shortly.
Sorry I didn't get this done for you last week. I hadn't looked
over the patch closely yet and didn't notice you were proposing
a new release.
Now that I've looked, I can say the changes all look fine to me.
I'm glad you broke up your recent patch into multiple commits.
I will publish your versioned release on oss.sgi.com today after
my tests complete.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-08-30 14:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <472498892.114291282107960876.JavaMail.root@mail-au.aconex.com>
2010-08-18 5:06 ` Review: xfsprogs with libblkid enabled for Debian nathans
2010-08-18 11:48 ` Dave Chinner
2010-08-19 12:11 ` Christoph Hellwig
2010-08-19 21:41 ` Nathan Scott
2010-08-26 13:26 ` Nathan Scott
2010-08-30 14:21 ` Alex Elder [this message]
2010-08-30 19:51 ` 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=1283178097.5273.97.camel@doink \
--to=aelder@sgi.com \
--cc=nathans@aconex.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