From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/eapi/
Date: Fri, 25 Feb 2022 19:04:36 +0000 (UTC) [thread overview]
Message-ID: <1645815765.e36a0545130215a7390dabaa5540d54c3a153c3f.sam@gentoo> (raw)
commit: e36a0545130215a7390dabaa5540d54c3a153c3f
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Fri Feb 25 19:02:45 2022 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Fri Feb 25 19:02:45 2022 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e36a0545
ebuild-writing/eapi: update link to Python guide
Migrated to projects.gentoo.org.
Signed-off-by: Sam James <sam <AT> gentoo.org>
ebuild-writing/eapi/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-writing/eapi/text.xml b/ebuild-writing/eapi/text.xml
index fbf88a5..2a716ae 100644
--- a/ebuild-writing/eapi/text.xml
+++ b/ebuild-writing/eapi/text.xml
@@ -80,7 +80,7 @@ or its dependencies.
The Base System project has
<uri link="https://wiki.gentoo.org/wiki/Project:Base#Rules_and_limitations">rules</uri>
governing their use of newer EAPIs, as does the
-<uri link="https://dev.gentoo.org/~mgorny/python-guide/package-maintenance.html#porting-packages-to-a-new-eapi">Python project</uri>.
+<uri link="https://projects.gentoo.org/python/guide/package-maintenance.html#porting-packages-to-a-new-eapi">Python project</uri>.
</p>
<p>
next reply other threads:[~2022-02-25 19:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-25 19:04 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-05 20:15 [gentoo-commits] proj/devmanual:master commit in: ebuild-writing/eapi/ Ulrich Müller
2022-11-09 12:01 Ulrich Müller
2022-02-22 7:11 Sam James
2022-02-22 7:11 Sam James
2020-05-09 10:41 Ulrich Müller
2020-01-23 7:47 Ulrich Müller
2020-01-09 7:58 Ulrich Müller
2018-10-24 13:01 Brian Evans
2017-09-25 4:27 Göktürk Yüksek
2017-01-25 0:55 Göktürk Yüksek
2016-12-08 4:07 Göktürk Yüksek
2016-09-08 21:23 Mike Gilbert
2016-04-30 3:09 Göktürk Yüksek
2016-03-24 15:10 Ulrich Müller
2016-02-15 18:00 Ulrich Müller
2016-02-15 12:10 Ulrich Müller
2016-02-15 12:10 Ulrich Müller
2015-11-22 12:37 Ulrich Müller
2014-06-08 17:39 Mike Gilbert
2013-04-30 12:58 Fabian Groffen
2013-01-21 17:27 Pacho Ramos
2013-01-21 8:18 Pacho Ramos
2012-11-17 18:59 Markos Chandras
2012-11-17 18:59 Markos Chandras
2012-11-02 17:53 Markos Chandras
2012-10-30 19:01 Markos Chandras
2012-08-31 21:18 Markos Chandras
2011-08-24 20:13 Markos Chandras
2011-03-09 16:42 Jeremy Olexa
2011-02-13 8:23 Torsten Veller
2011-02-04 20:41 darkside
2011-02-04 20:37 darkside
2011-02-04 17:02 darkside
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=1645815765.e36a0545130215a7390dabaa5540d54c3a153c3f.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