public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Aaron Bauman" <bman@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-fs/sshfs/
Date: Tue, 19 Nov 2019 00:39:09 +0000 (UTC)	[thread overview]
Message-ID: <1574123917.3586714a35b783e096e6dcafadbc79362ca631cc.bman@gentoo> (raw)

commit:     3586714a35b783e096e6dcafadbc79362ca631cc
Author:     Aaron Bauman <bman <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 19 00:38:37 2019 +0000
Commit:     Aaron Bauman <bman <AT> gentoo <DOT> org>
CommitDate: Tue Nov 19 00:38:37 2019 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3586714a

net-fs/sshfs: add myself as maintainer

Signed-off-by: Aaron Bauman <bman <AT> gentoo.org>

 net-fs/sshfs/metadata.xml | 11 +++++++----
 1 file changed, 7 insertions(+), 4 deletions(-)

diff --git a/net-fs/sshfs/metadata.xml b/net-fs/sshfs/metadata.xml
index f7daef81735..a23ff0249f7 100644
--- a/net-fs/sshfs/metadata.xml
+++ b/net-fs/sshfs/metadata.xml
@@ -1,8 +1,11 @@
 <?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
 <pkgmetadata>
-  <!-- maintainer-needed -->
-  <upstream>
-    <remote-id type="github">libfuse/sshfs</remote-id>
-  </upstream>
+	<maintainer type="person">
+		<email>bman@gentoo.org</email>
+		<name>Aaron Bauman</name>
+	</maintainer>
+	<upstream>
+		<remote-id type="github">libfuse/sshfs</remote-id>
+	</upstream>
 </pkgmetadata>


             reply	other threads:[~2019-11-19  0:39 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  0:39 Aaron Bauman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-08-13  7:10 [gentoo-commits] repo/gentoo:master commit in: net-fs/sshfs/ WANG Xuerui
2023-05-11 20:03 Sam James
2022-10-01  6:19 Arthur Zamarin
2022-09-25 11:17 Yixun Lan
2022-09-25  4:43 Sam James
2022-09-25  1:18 Sam James
2022-09-25  1:18 Sam James
2022-09-24 15:04 Arthur Zamarin
2022-09-24 13:46 Arthur Zamarin
2022-09-24 13:46 Arthur Zamarin
2022-09-14 19:18 Arthur Zamarin
2022-08-22 23:54 Yixun Lan
2022-08-14 13:31 Yixun Lan
2022-08-14 13:31 Yixun Lan
2022-08-14 12:58 Yixun Lan
2021-10-27  4:13 Sam James
2021-10-26  3:16 Sam James
2021-10-26  3:16 Sam James
2021-10-26  3:14 Sam James
2021-10-26  3:12 Sam James
2021-10-26  3:12 Sam James
2020-12-24  4:28 Tim Harder
2020-07-27 13:54 Sam James
2020-05-07  3:51 Tim Harder
2020-04-28 18:11 Sergei Trofimovich
2020-04-27  6:43 Agostino Sarubbo
2020-04-27  6:43 Agostino Sarubbo
2020-04-26 15:29 Agostino Sarubbo
2020-04-26 14:19 Agostino Sarubbo
2020-04-26 14:16 Agostino Sarubbo
2020-01-18  1:47 Tim Harder
2019-11-18 21:19 Tim Harder
2019-11-18 21:19 Tim Harder
2019-10-17 15:04 Göktürk Yüksek
2019-05-10 20:33 Tim Harder
2018-12-22 18:48 Tim Harder
2018-12-12  4:13 Tim Harder
2018-11-19  7:24 Mikle Kolyada
2018-11-07 23:44 Thomas Deutschmann
2018-11-06 23:56 Sergei Trofimovich
2018-11-06  6:57 Mikle Kolyada
2018-06-13  2:23 Tim Harder
2018-03-31 18:50 Mart Raudsepp
2018-03-19 11:32 Tim Harder
2018-03-19 11:32 Tim Harder
2018-03-19 11:32 Tim Harder
2017-08-04  9:46 Tim Harder
2017-04-19  3:41 Tim Harder
2016-11-12  6:20 Tim Harder
2016-11-12  6:20 Tim Harder
2016-10-01 13:09 Jeroen Roovers
2016-10-01  7:54 Markus Meier

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=1574123917.3586714a35b783e096e6dcafadbc79362ca631cc.bman@gentoo \
    --to=bman@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