From: "Georgy Yakovlev" <gyakovlev@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-process/minicoredumper/
Date: Fri, 21 Aug 2020 22:11:07 +0000 (UTC) [thread overview]
Message-ID: <1598047853.3f7e53c712e176c7daa79e7fa24fbb35759165d8.gyakovlev@gentoo> (raw)
commit: 3f7e53c712e176c7daa79e7fa24fbb35759165d8
Author: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
AuthorDate: Fri Aug 21 22:10:53 2020 +0000
Commit: Georgy Yakovlev <gyakovlev <AT> gentoo <DOT> org>
CommitDate: Fri Aug 21 22:10:53 2020 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3f7e53c7
sys-process/minicoredumper: update metadata.xml
git repo moved to github
Package-Manager: Portage-3.0.4, Repoman-3.0.1
Signed-off-by: Georgy Yakovlev <gyakovlev <AT> gentoo.org>
sys-process/minicoredumper/metadata.xml | 3 +++
1 file changed, 3 insertions(+)
diff --git a/sys-process/minicoredumper/metadata.xml b/sys-process/minicoredumper/metadata.xml
index c514535249c..da51470e12e 100644
--- a/sys-process/minicoredumper/metadata.xml
+++ b/sys-process/minicoredumper/metadata.xml
@@ -10,4 +10,7 @@
It can produce much smaller core dump files by making use of sparse files, compression,
and allowing the user to configure what parts of the process memory image should be dumped.
</longdescription>
+ <upstream>
+ <remote-id type="github">diamon/minicoredumper</remote-id>
+ </upstream>
</pkgmetadata>
next reply other threads:[~2020-08-21 22:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-21 22:11 Georgy Yakovlev [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-03-21 2:41 [gentoo-commits] repo/gentoo:master commit in: sys-process/minicoredumper/ Sam James
2023-01-04 1:13 Georgy Yakovlev
2020-05-29 9:45 Georgy Yakovlev
2020-01-14 7:43 Georgy Yakovlev
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=1598047853.3f7e53c712e176c7daa79e7fa24fbb35759165d8.gyakovlev@gentoo \
--to=gyakovlev@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