linux-xfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Dave Chinner <david@fromorbit.com>,
	Brian Foster <bfoster@redhat.com>,
	linux-xfs@vger.kernel.org, xfs@oss.sgi.com, amir73il@gmail.com
Subject: Re: XFS reflink and development tip git trees updated
Date: Tue, 27 Sep 2016 08:36:35 -0700	[thread overview]
Message-ID: <20160927153635.GI14092@birch.djwong.org> (raw)
In-Reply-To: <20160927142726.GA5675@infradead.org>

On Tue, Sep 27, 2016 at 07:27:26AM -0700, Christoph Hellwig wrote:
> On Mon, Sep 26, 2016 at 10:23:44PM -0700, Darrick J. Wong wrote:
> > Ok, here's this week's for-4.9 branch:
> > 
> > https://github.com/djwong/linux/tree/for-dave-for-4.9-5
> > https://github.com/djwong/xfsprogs/tree/for-dave-for-4.9-5
> > 
> > The kernel tree includes Christoph's fixes for copy-on-write,
> > refactoring of a refcount btree function to use _btree_query_range (and
> > inclusion of the required diff_two_keys/init_high_key helpers), and
> > removal of the (totally broken) always_cow debug switch.  It also
> > contains a new error injection point to make reflink fail with ENOSPC.
> 
> Are you going to send out the patches to the list?

Yeah, I'll spam^Wmail the list once more today.

> Also it seems like the writeback updates weren't folded in but just
> added to the end, was that intentional?

Yes -- both because I'm trying to limit the number of changes to the
patches in the middle that Dave might be reviewing, and also to get
all the combined fixes out for testing quicker.

(Don't worry, I'm already working on a 4.9-6 with these things cleaned
up.)

--D

      reply	other threads:[~2016-09-27 15:37 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-09-05  5:33 XFS reflink and development tip git trees updated Darrick J. Wong
2016-09-09  5:24 ` XFS reflink and getfsmap/scrub development git trees updated again Darrick J. Wong
2016-09-19 16:11 ` XFS reflink and development tip git trees updated Christoph Hellwig
2016-09-19 16:26   ` Darrick J. Wong
2016-09-20  4:39   ` Darrick J. Wong
2016-09-27  5:23     ` Darrick J. Wong
2016-09-27 14:27       ` Christoph Hellwig
2016-09-27 15:36         ` 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=20160927153635.GI14092@birch.djwong.org \
    --to=darrick.wong@oracle.com \
    --cc=amir73il@gmail.com \
    --cc=bfoster@redhat.com \
    --cc=david@fromorbit.com \
    --cc=hch@infradead.org \
    --cc=linux-xfs@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).