On 8/24/22 12:09, Coly Li wrote: > > >> 2022年8月24日 23:56,Jes Sorensen <jes@xxxxxxxxxxxxxxxxxx> 写道: >>> Hi Jes, >>> >>> Please check the version I post to you in series “mdadm-CI for-jes/20220728: patches for merge” (Message-Id: <20220728122101.28744-1-colyli@xxxxxxx>), the patch in this series is rebased and confirmed with Mateusz, it could be applied to upstream mdadm. > >> I applied this one, but none of the versions applied cleanly. I had to >> play formail games to pull it out of your stack, as I am not going to >> apply a set of 23 commits in one batch without going through them. > > These days I was in partner’s office and planed to repost the rebased version soon. If you don’t do the rebase yet, please wait for me to post a v4 version on behavior of Mateusz tomorrow. No worries, I already pulled some of it in, but you can check my repo and see whats there. >> It's really awesome to have your help reviewing patches, much >> appreciated, but I would prefer to keep them in the original batches so >> I can pull them from patchwork, rather than trying to deal with the >> giant stack. > > How about we improve the process like this, > 1) I will continue to review and response the patches from the original emails, so patch work may track them as they were. > 2) For all the reviewed patches are not handled by your after a period, let’s set it as 2 weeks for now, I will post a email with all the patches with their message-IDs to you as a remind. This sounds good to me! I think it's also fine to have a branch with everything applied for testing, it's just less easy for me to pull from. Thanks, Jes