On Tue, Oct 1, 2019 at 1:50 PM J. Bruce Fields <bfields@xxxxxxxxxx> wrote: > > On Tue, Oct 01, 2019 at 01:47:22PM -0400, Olga Kornievskaia wrote: > > On Tue, Oct 1, 2019 at 1:13 PM J. Bruce Fields <bfields@xxxxxxxxxxxx> wrote: > > > > > > On Mon, Sep 30, 2019 at 03:06:11PM -0400, Olga Kornievskaia wrote: > > > > Have you had a chance to take a look at the new patch series and have > > > > any more comments? > > > > > > Honestly, last time I checked I was having trouble finding things to > > > complain about--it looked OK to me. > > > > > > But I'm not sure I understood the management of copy id's, should I > > > should give it one more read. And then agree on how to merge it. > > > > Let me know what you would like to discuss about how copy ids are > > managed on the server. I thought that cover letter plus commit > > descriptions talk about how copy stateids and copy_notify states are > > managed. Do you want me to cut and paste that together here? Yes I did > > skip putting the same summary in v7 as I did in earlier submissions. > > You did fine, I just need to read it carefully and make sure I > understand. Ok. > > > I was thinking maybe you could give us a git branch based on 5.5-rc1 or > > > 5.5-rc2, Trond (I think it's Trond this time?) could pull the client > > > ones into his tree, and I could pull the rest into mine. > > > > I do have git space on linux-nfs so I could put my patches there. > > However, I'm confused about the ask to be based on 5.5-rc1 as we are > > still on 5.4-rc. > > Whoops, sorry, just a typo, I meant 5.4-rc. Ok. I have them in git://git.linux-nfs.org/projects/aglo/linux.git linux-ssc-for-5.5 branch. > > --b.
