From: "Darrick J. Wong" <darrick.wong@oracle.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Andreas Gruenbacher <agruenba@redhat.com>,
xfs <linux-xfs@vger.kernel.org>
Subject: Re: [ANNOUNCE] xfs-linux: for-next updated to a0e336ba3e3d
Date: Sun, 5 Aug 2018 09:08:58 -0700 [thread overview]
Message-ID: <20180805160858.GZ30972@magnolia> (raw)
In-Reply-To: <20180805073714.GA7787@infradead.org>
On Sun, Aug 05, 2018 at 12:37:14AM -0700, Christoph Hellwig wrote:
> On Sat, Aug 04, 2018 at 04:25:26PM +0200, Andreas Gruenbacher wrote:
> > > Did you rebase the tree? We really need to keep the iomap base
> > > branch stable as the gfs2 tree is also based on it and we want to avoid
> > > duplicate commits.
> >
> > Those hashes look okay to me. We only depend on the iomap-4.19-merge
> > branch, and that hasn't changed in a while and is still consistent
> > with the gfs2 for-next branch.
>
> Ok, I guess we are fine then. Listing these as new comments just
> looked suspicious.
Oops, yeah, sorry. When I generated the announce message I forgot to
tell git to start from the iomap branch merge instead of 'v4.18-rc4'.
Sorry about that; the iomap stuff are all the same patches from before.
--D
> --
> To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2018-08-05 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-03 19:17 [ANNOUNCE] xfs-linux: for-next updated to a0e336ba3e3d Darrick J. Wong
2018-08-04 9:06 ` Christoph Hellwig
2018-08-04 14:25 ` Andreas Gruenbacher
2018-08-05 7:37 ` Christoph Hellwig
2018-08-05 16:08 ` 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=20180805160858.GZ30972@magnolia \
--to=darrick.wong@oracle.com \
--cc=agruenba@redhat.com \
--cc=hch@infradead.org \
--cc=linux-xfs@vger.kernel.org \
/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).