public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Joonas Niilola" <juippis@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: sys-power/nut/
Date: Mon, 11 Dec 2023 13:04:05 +0000 (UTC)	[thread overview]
Message-ID: <1702299483.d20e5788358b90edc2545386d0704981699f539c.juippis@gentoo> (raw)

commit:     d20e5788358b90edc2545386d0704981699f539c
Author:     Francisco Javier Félix <web <AT> inode64 <DOT> com>
AuthorDate: Fri Sep 15 12:58:20 2023 +0000
Commit:     Joonas Niilola <juippis <AT> gentoo <DOT> org>
CommitDate: Mon Dec 11 12:58:03 2023 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=d20e5788

sys-power/nut: Rename asciidoc-ready documentation sources to *.adoc

https://github.com/networkupstools/nut/commit/83f3d8b18143baea8da0584ab11f3a4f59f56738

Signed-off-by: INODE64 <web <AT> inode64.com>
Closes: https://github.com/gentoo/gentoo/pull/32800
Signed-off-by: Joonas Niilola <juippis <AT> gentoo.org>

 sys-power/nut/nut-9999.ebuild | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/sys-power/nut/nut-9999.ebuild b/sys-power/nut/nut-9999.ebuild
index 1d0b5e50edae..a56635519b2d 100644
--- a/sys-power/nut/nut-9999.ebuild
+++ b/sys-power/nut/nut-9999.ebuild
@@ -187,11 +187,11 @@ src_install() {
 		mv "${i}" "${i/.sample/}" || die
 	done
 
-	local DOCS=( AUTHORS MAINTAINERS NEWS README TODO UPGRADING )
+	local DOCS=( AUTHORS MAINTAINERS NEWS.adoc README.adoc TODO.adoc UPGRADING.adoc )
 	einstalldocs
 
 	if use doc; then
-		newdoc lib/README README.lib
+		newdoc lib/README.adoc
 		dodoc docs/*.txt
 		docinto cables
 		dodoc docs/cables/*


             reply	other threads:[~2023-12-11 13:04 UTC|newest]

Thread overview: 64+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-11 13:04 Joonas Niilola [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-02-25  8:49 [gentoo-commits] repo/gentoo:master commit in: sys-power/nut/ Sam James
2025-01-24  8:14 Sam James
2024-10-12 11:22 Michał Górny
2024-10-12 10:08 Michał Górny
2024-10-12  7:52 Michał Górny
2024-05-29 18:27 Robin H. Johnson
2024-05-27 21:08 Robin H. Johnson
2024-05-27 21:08 Robin H. Johnson
2024-02-06  6:54 Sam James
2024-02-06  6:47 Sam James
2024-02-06  6:25 Sam James
2024-02-06  6:25 Sam James
2024-01-17  2:46 Ionen Wolkens
2024-01-01  0:12 Sam James
2023-12-18 13:36 Joonas Niilola
2023-12-18  1:09 Sam James
2023-12-18  0:11 Sam James
2023-08-09  3:34 Sam James
2023-06-24  1:18 Sam James
2023-06-17 17:11 Arthur Zamarin
2023-06-17 17:11 Arthur Zamarin
2023-06-17 15:48 Arthur Zamarin
2023-06-17 10:33 Yixun Lan
2023-06-17  3:56 Sam James
2023-06-17  3:55 Sam James
2023-06-17  3:19 Sam James
2022-06-21 18:21 Arthur Zamarin
2021-09-21 21:57 Marek Szuba
2021-08-18 14:28 Sam James
2021-08-04 19:37 Sam James
2021-07-09 22:36 Conrad Kostecki
2021-07-09 22:36 Conrad Kostecki
2020-08-30  1:17 Sam James
2020-08-22 15:51 Michał Górny
2020-08-11 18:46 Sam James
2020-08-10 14:33 Agostino Sarubbo
2020-08-07 18:51 Sam James
2020-02-19 18:24 Robin H. Johnson
2020-02-09 16:42 Michał Górny
2020-01-08 22:27 David Seifert
2020-01-08 22:27 David Seifert
2019-08-20 11:47 Louis Sautier
2019-08-13 12:10 Michał Górny
2019-07-29 10:45 Mikle Kolyada
2019-07-02  8:28 Sergei Trofimovich
2019-07-02  8:24 Sergei Trofimovich
2019-06-29 13:03 Agostino Sarubbo
2019-06-28 15:21 Agostino Sarubbo
2018-11-18 15:27 Thomas Deutschmann
2018-11-14 18:23 Robin H. Johnson
2018-10-27 19:02 Andreas Sturmlechner
2018-03-15 16:13 Mikle Kolyada
2018-01-15 19:03 Tobias Klausmann
2018-01-08 22:50 Thomas Deutschmann
2018-01-08 22:24 Sergei Trofimovich
2017-12-08 22:34 Matt Thode
2017-11-26 23:26 David Seifert
2017-03-21 12:57 Michael Weber
2016-12-20 18:21 Thomas Deutschmann
2016-12-20 17:31 Tobias Klausmann
2016-10-02 12:37 Pacho Ramos
2016-03-18 19:11 Michał Górny
2015-09-03  4:53 Matt Thode

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=1702299483.d20e5788358b90edc2545386d0704981699f539c.juippis@gentoo \
    --to=juippis@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