From: "Mike Gilbert" <floppym@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-fs/genfstab/
Date: Tue, 10 May 2022 18:50:18 +0000 (UTC) [thread overview]
Message-ID: <1652208613.232fa14f3af9b9acb77905eeb063ab9dad5de636.floppym@gentoo> (raw)
commit: 232fa14f3af9b9acb77905eeb063ab9dad5de636
Author: Mike Gilbert <floppym <AT> gentoo <DOT> org>
AuthorDate: Tue May 10 18:49:54 2022 +0000
Commit: Mike Gilbert <floppym <AT> gentoo <DOT> org>
CommitDate: Tue May 10 18:50:13 2022 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=232fa14f
sys-fs/genfstab: update HOMEPAGE, SRC_URI
Closes: https://bugs.gentoo.org/843452
Signed-off-by: Mike Gilbert <floppym <AT> gentoo.org>
sys-fs/genfstab/genfstab-24.ebuild | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/sys-fs/genfstab/genfstab-24.ebuild b/sys-fs/genfstab/genfstab-24.ebuild
index b0dcb0a50058..2981f73bb2c5 100644
--- a/sys-fs/genfstab/genfstab-24.ebuild
+++ b/sys-fs/genfstab/genfstab-24.ebuild
@@ -1,11 +1,11 @@
-# Copyright 1999-2021 Gentoo Authors
+# Copyright 1999-2022 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
EAPI=7
DESCRIPTION="Genfstab - generate output suitable for addition to an fstab file"
-HOMEPAGE="https://github.com/scardracs/genfstab https://man.archlinux.org/man/genfstab.8"
-SRC_URI="https://github.com/scardracs/genfstab/releases/download/${PV}/${P}.tar.gz"
+HOMEPAGE="https://github.com/mscardovi/genfstab https://man.archlinux.org/man/genfstab.8"
+SRC_URI="https://github.com/mscardovi/genfstab/releases/download/${PV}/${P}.tar.gz"
S="${WORKDIR}"
LICENSE="GPL-2"
next reply other threads:[~2022-05-10 18:50 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-10 18:50 Mike Gilbert [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-07-13 9:13 [gentoo-commits] repo/gentoo:master commit in: sys-fs/genfstab/ Sam James
2025-07-13 8:58 Sam James
2025-04-28 14:01 Sam James
2025-04-28 12:36 Arthur Zamarin
2025-04-28 5:33 Sam James
2025-04-28 4:37 Sam James
2025-04-28 4:35 Sam James
2025-04-28 4:33 Sam James
2024-11-23 15:27 Sam James
2024-11-23 15:27 Sam James
2024-01-30 18:30 Sam James
2024-01-30 9:20 Sam James
2024-01-26 2:09 Ionen Wolkens
2024-01-24 6:16 Sam James
2024-01-24 6:16 Sam James
2024-01-24 6:16 Sam James
2024-01-23 19:13 Arthur Zamarin
2024-01-23 18:58 Arthur Zamarin
2024-01-09 2:55 Sam James
2024-01-05 18:16 Arthur Zamarin
2024-01-05 10:14 Jakov Smolić
2024-01-05 8:18 Sam James
2024-01-05 8:16 Sam James
2024-01-05 8:14 Sam James
2023-12-19 7:31 Joonas Niilola
2023-12-18 7:21 Joonas Niilola
2023-12-18 1:09 Sam James
2023-12-18 0:11 Sam James
2023-09-12 19:28 WANG Xuerui
2023-03-03 5:45 Matt Turner
2023-02-24 18:58 Sam James
2023-02-24 18:58 Sam James
2023-02-24 16:54 Sam James
2023-02-24 16:54 Sam James
2023-02-24 16:54 Sam James
2023-02-24 15:55 Sam James
2023-01-14 23:25 Sam James
2022-12-21 15:13 Matt Turner
2022-12-21 15:13 Matt Turner
2022-12-21 15:13 Matt Turner
2022-11-29 22:09 Matt Turner
2022-11-17 12:36 Joonas Niilola
2021-11-29 7:12 Joonas Niilola
2021-11-26 23:22 Matt Turner
2021-07-13 20:05 Sam James
2021-07-11 20:51 Sam James
2021-07-11 8:58 Agostino Sarubbo
2021-06-13 5:56 Matt Turner
2021-05-20 5:19 Joonas Niilola
2021-05-02 15:25 Matt Turner
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=1652208613.232fa14f3af9b9acb77905eeb063ab9dad5de636.floppym@gentoo \
--to=floppym@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