From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/qa-scripts:master commit in: htdocs/
Date: Sat, 19 Mar 2022 22:18:27 +0000 (UTC) [thread overview]
Message-ID: <1647728294.ba92bba77ba90ede141ee48fdaa0caff6813ea8c.sam@gentoo> (raw)
commit: ba92bba77ba90ede141ee48fdaa0caff6813ea8c
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sat Mar 19 22:17:51 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Mar 19 22:18:14 2022 +0000
URL: https://gitweb.gentoo.org/proj/qa-scripts.git/commit/?id=ba92bba7
htdocs/index.html: update link to new eapi-usage/ directory
Contains STATS.txt for the old content but also per-EAPI files
listing ebuilds.
Signed-off-by: Sam James <sam <AT> gentoo.org>
htdocs/index.html | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/htdocs/index.html b/htdocs/index.html
index 3652d33..f6289de 100644
--- a/htdocs/index.html
+++ b/htdocs/index.html
@@ -143,7 +143,7 @@
<div class="col-lg-4">
<h3>Tree-wide Scanning</h3>
<div class="list-group mb-3">
- <a href="/output/eapi_usage.txt" class="list-group-item list-group-item-action">EAPI Usage</a>
+ <a href="/output/eapi-usage/" class="list-group-item list-group-item-action">EAPI Usage</a>
<a href="/output/eapi-per-eclass" class="list-group-item list-group-item-action">EAPI Usage per eclass</a>
<a href="/output/eapi-per-eclass/matrix.txt" class="list-group-item list-group-item-action">Eclass-EAPI usage matrix</a>
<a href="/output/invalid-mask.txt" class="list-group-item list-group-item-action">Invalid package.mask entries</a>
next reply other threads:[~2022-03-19 22:18 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-19 22:18 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-03-17 8:33 [gentoo-commits] proj/qa-scripts:master commit in: htdocs/ Michał Górny
2024-06-08 14:14 Michał Górny
2024-06-08 14:14 Michał Górny
2023-06-01 5:42 Sam James
2023-05-24 12:00 Sam James
2023-01-22 6:44 Sam James
2023-01-13 7:44 Sam James
2023-01-12 17:52 Ulrich Müller
2023-01-12 17:23 Ulrich Müller
2022-05-16 16:12 Michał Górny
2022-05-16 16:12 Michał Górny
2022-05-10 16:30 Sam James
2022-04-13 6:19 Sam James
2022-02-27 19:27 Robin H. Johnson
2021-11-09 7:41 Sam James
2021-11-09 7:41 Sam James
2021-11-09 7:03 Sam James
2021-11-09 7:00 Sam James
2020-10-23 7:08 Michał Górny
2020-06-02 17:37 Michał Górny
2020-06-02 14:32 Michał Górny
2020-06-02 6:31 Michał Górny
2020-05-25 12:22 Michał Górny
2020-05-11 0:38 Max Magorsch
2020-03-11 7:06 Mikle Kolyada
2019-09-01 8:12 Michał Górny
2019-09-01 8:12 Michał Górny
2019-07-17 13:30 Michał Górny
2019-07-03 12:46 Michał Górny
2019-06-11 10:27 Ulrich Müller
2019-04-19 13:17 Brian Evans
2019-04-19 13:17 Brian Evans
2018-08-12 10:42 Michał Górny
2018-07-18 10:36 Michał Górny
2018-07-18 7:15 Michał Górny
2018-07-17 16:09 Michał Górny
2018-07-17 16:09 Michał Górny
2018-07-17 16:09 Michał Górny
2018-07-17 16:09 Michał Górny
2018-07-17 15:43 Michał Górny
2018-05-08 21:11 Michał Górny
2018-01-06 11:29 Ulrich Müller
2018-01-06 11:29 Ulrich Müller
2017-10-02 15:24 Michał Górny
2015-12-25 20:08 Alex Legler
2015-04-25 10:59 Alex Legler
2014-08-28 19:16 Jorge Manuel B. S. Vicetto
2013-09-29 20:11 Markos Chandras
2013-06-21 18:02 Michael Palimaka
2013-02-14 16:15 Tomas Chvatal
2012-12-26 13:55 Jeremy Olexa
2012-11-28 12:15 Jeremy Olexa
2011-03-29 22:33 Christian Ruppert
2011-03-29 22:24 Christian Ruppert
2011-03-29 20:00 Tomas Chvatal
2011-03-29 19:48 Tomas Chvatal
2011-03-27 2:46 Jeremy Olexa
2011-03-22 16:06 Jeremy Olexa
2011-03-22 15:30 Jeremy Olexa
2011-03-21 15:02 Jeremy Olexa
2011-03-19 13:23 Tomas Chvatal
2011-03-18 21:00 Jeremy Olexa
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=1647728294.ba92bba77ba90ede141ee48fdaa0caff6813ea8c.sam@gentoo \
--to=sam@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