On Tue, Sep 24, 2019 at 09:46:15AM +0200, David Sterba wrote: > On Mon, Sep 23, 2019 at 02:21:04PM -0400, Josef Bacik wrote: > > > I got some strange merge conflicts, it turns out patch 6/9 did not make > > > it to the mailinglist (nor patchwork where I could pick it eventually). > > > For that it's useful to have the list of commits too along with the > > > diffstat, ie. what format-patch generates. > > > > Huh weird. I see you merged up through patch 5, I'll rebase and resend and > > maybe this time the ML will take it. > > Yeah I merged what I had, even some of the 7-9 applied but that could > cause conflicts after your changes. > > > How about I start sending pull requests through github for everything in > > addition to sending stuff to the mailinglist, that way it's easier to track the > > bigger things? Thanks, > > You can always send a link to git branch with the patches, not only for > cases like that, but we also want the mailig list copy. I almost always > process the mailinglist to send replies and to check previous > iterations. IOW, git branch is for convenience. Yeah I'm not saying replace the mailinglist stuff, but augment it with a github PR to make sure things don't get lost. I'll follow up with that shortly. Josef
