From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/valgrind/files/
Date: Mon, 23 Jan 2023 01:11:19 +0000 (UTC) [thread overview]
Message-ID: <1674436221.3bc35e7313ee1b5f20454cf7c920b071854752b2.sam@gentoo> (raw)
commit: 3bc35e7313ee1b5f20454cf7c920b071854752b2
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Mon Jan 23 01:10:21 2023 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Mon Jan 23 01:10:21 2023 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3bc35e73
dev-util/valgrind: drop misleading provenance comment in musl malloc patch
Per https://git.alpinelinux.org/aports/commit/main/valgrind?id=cd20c3c60433fd20b7e57723575a5944dc6ae42f,
this patch actually originated in Gentoo, so saying it's from Alpine is confusing.
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/valgrind/files/valgrind-3.13.0-malloc.patch | 2 --
1 file changed, 2 deletions(-)
diff --git a/dev-util/valgrind/files/valgrind-3.13.0-malloc.patch b/dev-util/valgrind/files/valgrind-3.13.0-malloc.patch
index ac6d90fef50f..d0eb795b84be 100644
--- a/dev-util/valgrind/files/valgrind-3.13.0-malloc.patch
+++ b/dev-util/valgrind/files/valgrind-3.13.0-malloc.patch
@@ -1,5 +1,3 @@
-From: https://git.alpinelinux.org/aports/tree/main/valgrind/
-
--- valgrind-3.13.0/coregrind/m_replacemalloc/vg_replace_malloc.c
+++ valgrind-3.13.0/coregrind/m_replacemalloc/vg_replace_malloc.c
@@ -765,13 +765,15 @@ static void init(void);
next reply other threads:[~2023-01-23 1:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-23 1:11 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-02-08 17:17 [gentoo-commits] repo/gentoo:master commit in: dev-util/valgrind/files/ Sam James
2022-07-27 13:47 Anthony G. Basile
2020-05-30 23:32 Anthony G. Basile
2017-08-09 12:18 Anthony G. Basile
2016-04-16 8:51 Anthony G. Basile
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=1674436221.3bc35e7313ee1b5f20454cf7c920b071854752b2.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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