From: Derrick Stolee <stolee@gmail.com>
To: Emily Shaffer <emilyshaffer@google.com>,
Josh Steadmon <steadmon@google.com>
Cc: git@vger.kernel.org, avarab@gmail.com
Subject: Re: [PATCH] commit-graph: fix memory leak
Date: Mon, 6 May 2019 21:58:18 -0400 [thread overview]
Message-ID: <56cd0368-1011-f06a-770c-f62b138e8627@gmail.com> (raw)
In-Reply-To: <20190506215831.GB85211@google.com>
On 5/6/2019 5:58 PM, Emily Shaffer wrote:
> Hi,
>
> This change looks good to me, and like good evidence for the benefits of
> automated tooling :)
Same here! Keep up the great work here.
-Stolee
next prev parent reply other threads:[~2019-05-07 1:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-06 21:36 [PATCH] commit-graph: fix memory leak Josh Steadmon
2019-05-06 21:58 ` Emily Shaffer
2019-05-07 1:58 ` Derrick Stolee [this message]
2019-05-07 9:49 ` Ævar Arnfjörð Bjarmason
2019-05-07 22:26 ` Jeff King
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=56cd0368-1011-f06a-770c-f62b138e8627@gmail.com \
--to=stolee@gmail.com \
--cc=avarab@gmail.com \
--cc=emilyshaffer@google.com \
--cc=git@vger.kernel.org \
--cc=steadmon@google.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).