From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Eric Sandeen <sandeen@sandeen.net>
Cc: linux-xfs <linux-xfs@vger.kernel.org>,
Dave Chinner <dchinner@redhat.com>,
Christoph Hellwig <hch@infradead.org>
Subject: Re: [DEVEL] libxfs update timing for xfsprogs 5.8.0
Date: Fri, 24 Jul 2020 12:21:42 -0700 [thread overview]
Message-ID: <20200724192142.GK7625@magnolia> (raw)
In-Reply-To: <1088d142-1e80-aaac-62eb-2b01f0fc9c63@sandeen.net>
On Fri, Jul 24, 2020 at 12:08:21PM -0700, Eric Sandeen wrote:
> At one point there was a little discussion about whether it might
> be better to defer libxfs/ syncing to later in the release, rather
> than doing it at the beginning. I'm happy to do it either way.
>
> Do we have a preference for 5.8.0, would one be better than the other
> for anyone working on major xfsprogs updates?
>
> (Darrick probably already has his work staged on top of a libxfs
> sync, so there's that ...)
I wouldn't mind if the xfs_repair quotacheck stuff went in before the
libxfs sync... :)
--D
> -Eric
prev parent reply other threads:[~2020-07-24 19:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-24 19:08 [DEVEL] libxfs update timing for xfsprogs 5.8.0 Eric Sandeen
2020-07-24 19:21 ` Darrick J. Wong [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=20200724192142.GK7625@magnolia \
--to=darrick.wong@oracle.com \
--cc=dchinner@redhat.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
--cc=sandeen@sandeen.net \
/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;
as well as URLs for NNTP newsgroup(s).