public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/toolchain/linux-headers-patches:master commit in: /
Date: Tue, 29 Jul 2025 09:04:30 +0000 (UTC)	[thread overview]
Message-ID: <1753760800.4c5c61d71d050e78c57e02ee003cdfec3e780a3f.sam@gentoo> (raw)

commit:     4c5c61d71d050e78c57e02ee003cdfec3e780a3f
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Jul 29 03:46:29 2025 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Jul 29 03:46:40 2025 +0000
URL:        https://gitweb.gentoo.org/proj/toolchain/linux-headers-patches.git/commit/?id=4c5c61d7

testing.txt: dev-util/rr -> dev-debug/rr

Signed-off-by: Sam James <sam <AT> gentoo.org>

 testing.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/testing.txt b/testing.txt
index a142f75..2598865 100644
--- a/testing.txt
+++ b/testing.txt
@@ -58,7 +58,7 @@ dev-util/bootconfig
 dev-util/bpftool
 dev-util/oprofile
 dev-util/perf
-dev-util/rr
+dev-debug/rr
 dev-debug/strace
 dev-util/sysprof
 dev-util/sysprof-capture


             reply	other threads:[~2025-07-29  9:04 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-29  9:04 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-05-03  6:32 [gentoo-commits] proj/toolchain/linux-headers-patches:master commit in: / Sam James
2024-03-13  4:52 Sam James
2024-03-13  4:52 Sam James
2024-01-19 11:15 Sam James
2022-10-08 22:17 Sam James
2022-10-08 22:17 Sam James
2022-01-08  3:49 Sam James
2021-09-05  5:47 Sam James
2021-02-15 22:40 Sergei Trofimovich
2020-12-14  8:12 Sergei Trofimovich
2019-12-08 14:28 Sergei Trofimovich
2019-12-08 13:23 Sergei Trofimovich
2019-12-08 13:21 Sergei Trofimovich
2019-12-08 13:03 Sergei Trofimovich
2019-03-06 22:13 Sergei Trofimovich
2018-10-23 22:39 Sergei Trofimovich
2018-10-12 22:56 Sergei Trofimovich

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=1753760800.4c5c61d71d050e78c57e02ee003cdfec3e780a3f.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