On Thu, Nov 15, 2018 at 2:44 PM Andreas Gruenbacher wrote:
>
> Ok, I've changed the merge commit as follows now:
>
> Merge tag 'v4.20-rc1'
>
> Pull in the gfs2 fixes that went into v4.19-rc8:
>
> gfs2: Fix iomap buffered write support for journaled files
> gfs2: Fix iomap
On Thu, 15 Nov 2018 at 19:23, Linus Torvalds
wrote:
>
> On Thu, Nov 15, 2018 at 12:20 PM Andreas Gruenbacher
> wrote:
> >
> > I guess rebasing the for-next branch onto something more recent to
> > avoid the back-merge in the first place will be best, resulting in a
> > cleaner history.
>
>
On Thu, 15 Nov 2018 at 18:11, Linus Torvalds
wrote:
> On Thu, Nov 15, 2018 at 6:00 AM Andreas Gruenbacher
> wrote:
> >
> > could you please pull the following gfs2 fixes for 4.20?
>
> No.
>
> I'm not pulling this useless commit message:
>
> "Merge tag 'v4.20-rc1'"
>
> with absolutely _zero_
On Thu, Nov 15, 2018 at 12:20 PM Andreas Gruenbacher
wrote:
>
> I guess rebasing the for-next branch onto something more recent to
> avoid the back-merge in the first place will be best, resulting in a
> cleaner history.
Rebases aren't really any better at all.
If you have a real *reason* for a
On Thu, Nov 15, 2018 at 6:00 AM Andreas Gruenbacher wrote:
>
> could you please pull the following gfs2 fixes for 4.20?
No.
I'm not pulling this useless commit message:
"Merge tag 'v4.20-rc1'"
with absolutely _zero_ explanation for why that merge was done.
Guys, stop doing this. Because I
