From: Anthony Delannoy <anthony.2lannoy@gmail.com>
To: git@vger.kernel.org
Cc: Anthony Delannoy <anthony.2lannoy@gmail.com>
Subject: [PATCH 0/1] pathspec: fix memleak
Date: Fri, 12 Aug 2022 10:17:43 +0200 [thread overview]
Message-ID: <20220812081744.456280-1-anthony.2lannoy@gmail.com> (raw)
Sending this patch to fix a memleak, created with copy_pathspec, found
thanks to the address sanitizer.
Thanks
Anthony Delannoy (1):
pathspec: fix memleak
preload-index.c | 3 +++
1 file changed, 3 insertions(+)
base-commit: 5502f77b6944eda8e26813d8f542cffe7d110aea
--
2.35.1
next reply other threads:[~2022-08-12 8:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 8:17 Anthony Delannoy [this message]
2022-08-12 8:17 ` [PATCH 1/1] pathspec: fix memleak Anthony Delannoy
2022-08-12 17:41 ` Junio C Hamano
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=20220812081744.456280-1-anthony.2lannoy@gmail.com \
--to=anthony.2lannoy@gmail.com \
--cc=git@vger.kernel.org \
/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).