From: "Göktürk Yüksek" <gokturk@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/
Date: Sun, 22 Jan 2017 20:45:27 +0000 (UTC) [thread overview]
Message-ID: <1485117683.e098b2f260ebd9241be932dfcf93feb5db9d344b.gokturk@gentoo> (raw)
commit: e098b2f260ebd9241be932dfcf93feb5db9d344b
Author: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
AuthorDate: Sun Jan 22 20:41:23 2017 +0000
Commit: Göktürk Yüksek <gokturk <AT> gentoo <DOT> org>
CommitDate: Sun Jan 22 20:41:23 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=e098b2f2
ebuild-maintenance: fix the kernel patch submitting guidelines link
Reported-By: M. J. Everitt <m.j.everitt <AT> iee.org>
ebuild-maintenance/text.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ebuild-maintenance/text.xml b/ebuild-maintenance/text.xml
index 6d2e813..859b473 100644
--- a/ebuild-maintenance/text.xml
+++ b/ebuild-maintenance/text.xml
@@ -159,7 +159,7 @@ Finally the commit message should list auxiliary information such as
people who are involved in authoring, suggesting, reviewing and
testing the changes, and revelant bugs. Use RFC822/git style tags as
explained in the
-<uri link="https://www.kernel.org/doc/Documentation/SubmittingPatches">
+<uri link="https://kernel.org/doc/html/latest/process/submitting-patches.html">
Linux Kernel patch guideline</uri>. Additionally, the following tags
are used in Gentoo:
next reply other threads:[~2017-01-22 20:45 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-22 20:45 Göktürk Yüksek [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-01-23 8:40 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/ Ulrich Müller
2017-09-25 4:40 Göktürk Yüksek
2017-09-25 4:40 Göktürk Yüksek
2017-07-29 20:48 Göktürk Yüksek
2016-11-20 20:46 Göktürk Yüksek
2016-08-18 9:01 Ulrich Müller
2016-05-22 8:35 Ulrich Müller
2016-05-01 3:49 Göktürk Yüksek
2016-04-24 0:47 Göktürk Yüksek
2016-04-23 19:26 Göktürk Yüksek
2016-04-19 10:40 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2016-02-05 12:59 Ulrich Müller
2015-05-09 15:22 Ulrich Müller
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=1485117683.e098b2f260ebd9241be932dfcf93feb5db9d344b.gokturk@gentoo \
--to=gokturk@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