public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marek Szuba" <marecki@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: x11-misc/i3lock/
Date: Mon, 30 Nov 2020 12:01:08 +0000 (UTC)	[thread overview]
Message-ID: <1606735464.59473a6bfd4d853d6dc142ec93a4bbf3b2e974ca.marecki@gentoo> (raw)

commit:     59473a6bfd4d853d6dc142ec93a4bbf3b2e974ca
Author:     Jakov Smolic <jakov.smolic <AT> sartura <DOT> hr>
AuthorDate: Sun Nov 29 18:20:47 2020 +0000
Commit:     Marek Szuba <marecki <AT> gentoo <DOT> org>
CommitDate: Mon Nov 30 11:24:24 2020 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=59473a6b

x11-misc/i3lock: new maintainer

Package-Manager: Portage-3.0.9, Repoman-3.0.1
Signed-off-by: Jakov Smolic <jakov.smolic <AT> sartura.hr>
Signed-off-by: Marek Szuba <marecki <AT> gentoo.org>

 x11-misc/i3lock/metadata.xml | 8 ++++++--
 1 file changed, 6 insertions(+), 2 deletions(-)

diff --git a/x11-misc/i3lock/metadata.xml b/x11-misc/i3lock/metadata.xml
index 2ba8e9e851e..9654d1c22bc 100644
--- a/x11-misc/i3lock/metadata.xml
+++ b/x11-misc/i3lock/metadata.xml
@@ -1,8 +1,12 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
+	<maintainer type="person">
+		<email>jakov.smolic@sartura.hr</email>
+		<name>Jakov Smolic</name>
+	</maintainer>
 	<maintainer type="project">
-		<email>desktop-misc@gentoo.org</email>
-		<name>Gentoo Desktop Miscellaneous Project</name>
+		<email>proxy-maint@gentoo.org</email>
+		<name>Proxy Maintainers</name>
 	</maintainer>
 </pkgmetadata>


             reply	other threads:[~2020-11-30 12:01 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-30 12:01 Marek Szuba [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-26 12:24 [gentoo-commits] repo/gentoo:master commit in: x11-misc/i3lock/ Jakov Smolić
2024-08-25 13:59 Sam James
2024-08-25 13:59 Sam James
2024-04-07 18:26 Marek Szuba
2022-12-21 11:31 Marek Szuba
2022-11-10 22:40 Marek Szuba
2022-09-26  1:02 Marek Szuba
2022-07-23  2:50 Sam James
2022-06-30  9:02 Marek Szuba
2022-06-30  7:01 Agostino Sarubbo
2022-06-29 11:58 Sam James
2022-06-22 13:09 Jakov Smolić
2022-05-28 23:55 Marek Szuba
2022-05-28 23:55 Marek Szuba
2021-09-27 22:57 Marek Szuba
2021-08-27 23:13 Jakov Smolić
2021-01-07 10:14 David Seifert
2021-01-03  9:12 Sam James
2020-11-30 12:01 Marek Szuba
2020-11-30 12:01 Marek Szuba
2020-11-30 12:01 Marek Szuba
2020-01-14 22:48 Matt Turner
2019-12-26 12:56 Georgy Yakovlev
2019-10-12 20:44 Mikle Kolyada
2019-07-23 10:03 Jeroen Roovers
2018-10-20 11:14 Jeroen Roovers
2018-10-20 11:14 Jeroen Roovers
2018-10-12  9:16 Jeroen Roovers
2018-10-11 19:15 Johannes Huber
2018-06-26  6:53 Johannes Huber
2018-06-26  6:53 Johannes Huber
2018-06-23 18:34 Mikle Kolyada
2018-06-23  9:54 Johannes Huber
2018-06-04 19:25 Mart Raudsepp
2018-03-26 19:18 Aaron Bauman
2018-01-06 21:49 Markus Meier
2017-11-25  8:22 Jeroen Roovers
2017-06-27  7:53 Jeroen Roovers
2017-06-27  7:53 Jeroen Roovers
2017-06-20 12:53 Pacho Ramos
2017-06-04 21:32 Jeroen Roovers
2016-06-12 10:16 Jeroen Roovers
2016-06-12 10:16 Jeroen Roovers
2015-08-09 17:54 Mikle Kolyada

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=1606735464.59473a6bfd4d853d6dc142ec93a4bbf3b2e974ca.marecki@gentoo \
    --to=marecki@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