public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Thomas Deutschmann" <whissi@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/mdadm/
Date: Mon,  4 May 2020 17:36:11 +0000 (UTC)	[thread overview]
Message-ID: <1588613742.5e3add40478d1f743984b51e80e24ec76d7718a4.whissi@gentoo> (raw)

commit:     5e3add40478d1f743984b51e80e24ec76d7718a4
Author:     Roy Yang <royyang <AT> google <DOT> com>
AuthorDate: Sat May  2 22:16:51 2020 +0000
Commit:     Thomas Deutschmann <whissi <AT> gentoo <DOT> org>
CommitDate: Mon May  4 17:35:42 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=5e3add40

Fixed CPE tag for sys-fs/mdadm

Signed-off-by: Roy Yang <royyang <AT> google.com>
Signed-off-by: Thomas Deutschmann <whissi <AT> gentoo.org>

 sys-fs/mdadm/metadata.xml | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/sys-fs/mdadm/metadata.xml b/sys-fs/mdadm/metadata.xml
index 56c12441305..6923416f0f6 100644
--- a/sys-fs/mdadm/metadata.xml
+++ b/sys-fs/mdadm/metadata.xml
@@ -5,4 +5,7 @@
 	<email>base-system@gentoo.org</email>
 	<name>Gentoo Base System</name>
 </maintainer>
+<upstream>
+	<remote-id type="cpe">cpe:/a:mdadm_project:mdadm</remote-id>
+</upstream>
 </pkgmetadata>


             reply	other threads:[~2020-05-04 17:36 UTC|newest]

Thread overview: 78+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-04 17:36 Thomas Deutschmann [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-14 18:18 [gentoo-commits] repo/gentoo:master commit in: sys-fs/mdadm/ Sam James
2025-03-11 14:18 Sam James
2025-03-11 14:18 Sam James
2025-03-11 14:18 Sam James
2025-03-11 14:18 Sam James
2025-03-11 14:11 Sam James
2025-03-11 14:11 Sam James
2025-03-11 14:11 Sam James
2025-02-27  8:42 Sam James
2025-02-23  2:00 Sam James
2025-02-16  4:15 Sam James
2025-02-15 19:39 Jakov Smolić
2025-02-13 12:00 Sam James
2025-02-13 11:49 Sam James
2025-02-13 11:34 Sam James
2025-02-13 11:34 Sam James
2025-02-13 11:34 Sam James
2025-02-13 11:34 Sam James
2024-09-12 14:36 Arthur Zamarin
2024-09-12 14:36 Arthur Zamarin
2024-08-25 12:04 Andreas K. Hüttel
2024-04-17  5:37 Arthur Zamarin
2024-03-24 12:12 Sam James
2024-03-24 11:37 Sam James
2024-03-24 11:35 Sam James
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-03-24 11:29 Sam James
2024-03-03 16:50 Andreas K. Hüttel
2024-02-19 22:32 Robin H. Johnson
2024-02-19 21:00 Robin H. Johnson
2023-09-11 15:35 Mike Gilbert
2023-04-03 18:38 Arthur Zamarin
2023-04-03 18:38 Arthur Zamarin
2023-03-04  8:18 Arthur Zamarin
2023-03-04  7:17 Arthur Zamarin
2023-03-04  6:17 Arthur Zamarin
2023-03-04  5:59 Arthur Zamarin
2023-03-04  5:55 Arthur Zamarin
2022-05-19  7:28 WANG Xuerui
2022-04-17 17:06 Sam James
2022-01-03  7:48 Sam James
2022-01-01 15:15 Lars Wendler
2021-11-04 17:53 Lars Wendler
2021-09-18  1:43 Yixun Lan
2021-09-10 20:16 Matt Turner
2021-08-04  8:19 Lars Wendler
2021-08-03 11:03 Sam James
2021-04-15 21:36 Lars Wendler
2021-03-05 19:02 Lars Wendler
2020-12-14 18:29 Mike Gilbert
2020-08-19 20:22 Sam James
2019-11-25 16:00 Thomas Deutschmann
2019-10-05 18:56 Michał Górny
2018-11-30  8:04 Lars Wendler
2018-11-28 16:05 Tobias Klausmann
2018-11-18 10:38 Sergei Trofimovich
2018-11-13 21:12 Robin H. Johnson
2018-11-11 11:15 Mikle Kolyada
2018-11-08 23:35 Sergei Trofimovich
2018-11-07 23:44 Thomas Deutschmann
2018-11-07 22:41 Sergei Trofimovich
2018-11-07  0:17 Sergei Trofimovich
2018-11-07  0:15 Sergei Trofimovich
2018-11-06 21:35 Mikle Kolyada
2018-10-26 23:58 Lars Wendler
2018-08-15 15:05 Lars Wendler
2018-03-27  9:13 Lars Wendler
2017-12-01 22:19 David Seifert
2017-02-17  6:04 Markus Meier
2017-01-10 19:05 Lars Wendler
2017-01-10  6:55 Jeroen Roovers
2017-01-06 14:33 Tobias Klausmann
2016-12-29 10:05 Agostino Sarubbo
2016-02-08 23:44 Mike Frysinger
2016-01-28 10:22 Lars Wendler

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=1588613742.5e3add40478d1f743984b51e80e24ec76d7718a4.whissi@gentoo \
    --to=whissi@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