From: Jes Sorensen <jes@trained-monkey.org>
To: Coly Li <colyli@suse.de>
Cc: Mateusz Kusiak <mateusz.kusiak@intel.com>, linux-raid@vger.kernel.org
Subject: Re: [PATCH v3] Grow: Split Grow_reshape into helper function
Date: Wed, 24 Aug 2022 12:33:25 -0400 [thread overview]
Message-ID: <f732cc9e-65d5-2b8a-cd66-20f99bc2d625@trained-monkey.org> (raw)
In-Reply-To: <193A9B1E-ACB9-40C1-A6B0-BE0FC5C29753@suse.de>
On 8/24/22 12:09, Coly Li wrote:
>
>
>> 2022年8月24日 23:56,Jes Sorensen <jes@trained-monkey.org> 写道:
>>> 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@suse.de>), 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
next prev parent reply other threads:[~2022-08-24 16:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-09 7:41 [PATCH v3] Grow: Split Grow_reshape into helper function Mateusz Kusiak
2022-06-20 17:21 ` Coly Li
2022-06-28 15:56 ` Coly Li
2022-06-29 13:12 ` Kusiak, Mateusz
2022-06-29 13:14 ` Coly Li
2022-08-07 20:41 ` Jes Sorensen
2022-08-08 10:03 ` Coly Li
2022-08-15 19:18 ` Jes Sorensen
2022-08-24 15:56 ` Jes Sorensen
2022-08-24 16:09 ` Coly Li
2022-08-24 16:33 ` Jes Sorensen [this message]
2022-08-24 16:41 ` Coly Li
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f732cc9e-65d5-2b8a-cd66-20f99bc2d625@trained-monkey.org \
--to=jes@trained-monkey.org \
--cc=colyli@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=mateusz.kusiak@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.