lkml.org 
[lkml]   [2019]   [Sep]   [19]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
From
SubjectRe: [GIT PULL afs: Development for 5.4
Date
David Howells <dhowells@redhat.com> wrote:

> > However, I was close to unpulling it again. It has a merge commit with
> > this merge message:
> >
> > Merge remote-tracking branch 'net/master' into afs-next
> >
> > and that simply is not acceptable.
>
> Apologies - I meant to rebase that away. There was a bug fix to rxrpc in
> net/master that didn't get pulled into your tree until Saturday.

Actually, waiting for all outstanding fixes to get merged and then rebasing
might not be the right thing here. The problem is that there are fixes in
both trees: afs fixes go directly into yours whereas rxrpc fixes go via
networking and I would prefer to base my patches on both of them for testing
purposes. What's the preferred method for dealing with that? Base on a merge
of the lastest of those fixes in each tree?

David

\
 
 \ /
  Last update: 2019-09-19 11:50    [W:0.108 / U:1.832 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site