From: Derrick Stolee <stolee@gmail.com>
To: Ramsay Jones <ramsay@ramsayjones.plus.com>,
Derrick Stolee <dstolee@microsoft.com>
Cc: GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [PATCH] gc: fix some sparse 'symbol not declared' warnings
Date: Thu, 9 Jul 2020 07:21:46 -0400 [thread overview]
Message-ID: <1acadbb6-3c28-0ce0-7578-a0af2b034a3c@gmail.com> (raw)
In-Reply-To: <9c9164e2-0fff-7211-a79a-f4c546d2cedd@ramsayjones.plus.com>
On 7/8/2020 8:23 PM, Ramsay Jones wrote:
>
> Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
> ---
>
> Hi Derrick,
>
> If you need to re-roll your 'ds/maintenance' branch, could you please
> squash this into the relevant patches. The first hunk should be squashed
> into commit a138b8ff61 (maintenance: create basic maintenance runner,
> 2020-07-07) and the second hunk into commit aca963ff39 (maintenance:
> initialize task array and hashmap, 2020-07-07).
Can do, thanks! Sorry for the disruption.
-Stolee
prev parent reply other threads:[~2020-07-09 11:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-09 0:23 [PATCH] gc: fix some sparse 'symbol not declared' warnings Ramsay Jones
2020-07-09 11:21 ` Derrick Stolee [this message]
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=1acadbb6-3c28-0ce0-7578-a0af2b034a3c@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=ramsay@ramsayjones.plus.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).