Re: [ANNOUNCE] xfs-linux: for-next updated to a0e336ba3e3d

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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@xxxxxxxxxxxxxxx
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
--
To unsubscribe from this list: send the line "unsubscribe linux-xfs" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [XFS Filesystem Development (older mail)]     [Linux Filesystem Development]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux RAID]     [Linux SCSI]


  Powered by Linux