From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: dev-util/lttng-modules/
Date: Sat, 5 Nov 2022 06:27:24 +0000 (UTC) [thread overview]
Message-ID: <1667628613.2b316d5bd5d65012b92349d75bb3a98381f818be.sam@gentoo> (raw)
commit: 2b316d5bd5d65012b92349d75bb3a98381f818be
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Nov 5 05:56:48 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Nov 5 06:10:13 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=2b316d5b
dev-util/lttng-modules: add github upstream metadata
Signed-off-by: Sam James <sam <AT> gentoo.org>
dev-util/lttng-modules/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/dev-util/lttng-modules/metadata.xml b/dev-util/lttng-modules/metadata.xml
index a559bf3a7dcd..a3465ae4f01d 100644
--- a/dev-util/lttng-modules/metadata.xml
+++ b/dev-util/lttng-modules/metadata.xml
@@ -5,4 +5,7 @@
<longdescription>
Use the kernel tracer if you are debugging a system-wide performance problem or a kernel problem. This tracer comes with an instrumentation patch for most kernel subsystems, which is enough to debug many problems. This includes system calls, IRQs, traps, memory management, softIRQs, scheduling and many others. Of course, the kernel tracer allows you to add your own instrumentation anywhere in the kernel code.
</longdescription>
+ <upstream>
+ <remote-id type="github">lttng/lttng-modules</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2022-11-05 6:27 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-05 6:27 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-01-04 15:41 [gentoo-commits] repo/gentoo:master commit in: dev-util/lttng-modules/ Florian Schmaus
2025-01-04 15:41 Florian Schmaus
2025-01-04 15:41 Florian Schmaus
2024-11-05 9:02 Florian Schmaus
2024-11-05 9:02 Florian Schmaus
2024-08-27 13:13 Florian Schmaus
2024-08-27 12:04 Florian Schmaus
2024-07-19 6:05 Sam James
2023-06-28 11:47 Mike Pagano
2023-06-26 23:13 Mike Pagano
2023-06-26 17:45 Sam James
2023-06-24 20:34 Mike Pagano
2022-12-27 10:23 Sam James
2022-04-26 22:10 Yixun Lan
2022-04-26 8:06 Yixun Lan
2022-04-26 8:06 Yixun Lan
2021-11-22 14:12 Jakov Smolić
2021-09-26 8:50 Yixun Lan
2021-09-19 21:53 Sam James
2021-09-19 21:53 Sam James
2021-03-30 15:12 Yixun Lan
2019-10-23 9:47 Yixun Lan
2019-10-23 9:47 Yixun Lan
2019-10-22 9:58 Yixun Lan
2018-09-21 12:20 Thomas Deutschmann
2018-08-25 17:38 Michael Weber
2016-07-01 2:44 Yixun Lan
2016-06-21 12:43 Yixun Lan
2016-02-18 7:44 Yixun Lan
2016-02-18 7:44 Yixun Lan
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=1667628613.2b316d5bd5d65012b92349d75bb3a98381f818be.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