From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: general-concepts/news/
Date: Tue, 28 Nov 2017 22:52:23 +0000 (UTC) [thread overview]
Message-ID: <1511909430.1ca9b99efeabac3522d976ea94caef5b6b227c5d.ulm@gentoo> (raw)
commit: 1ca9b99efeabac3522d976ea94caef5b6b227c5d
Author: Ulrich Müller <ulm <AT> gentoo <DOT> org>
AuthorDate: Tue Nov 28 22:50:30 2017 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Nov 28 22:50:30 2017 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=1ca9b99e
general-concepts/news: Fix XML, rewrap long lines.
No text changes.
general-concepts/news/text.xml | 59 ++++++++++++++++++++++++++++++------------
1 file changed, 43 insertions(+), 16 deletions(-)
diff --git a/general-concepts/news/text.xml b/general-concepts/news/text.xml
index 2484ea8..2961084 100644
--- a/general-concepts/news/text.xml
+++ b/general-concepts/news/text.xml
@@ -5,14 +5,16 @@
<body>
<p>
-Gentoo News Items were created to provide a communication medium to push critical
-messages to users via the rsync tree. The original proposal for news items is outlined
-in <uri link="https://www.gentoo.org/glep/glep-0042.html">GLEP 42: Critical News Reporting.</uri>
+Gentoo News Items were created to provide a communication medium to push
+critical messages to users via the rsync tree. The original proposal for news
+items is outlined in <uri link="https://www.gentoo.org/glep/glep-0042.html">
+GLEP 42: Critical News Reporting.</uri>
</p>
<p>
-News Items can be read using the eselect command. More information on use of this tool to
-read or delete news items can be found on the news.eselect man page.
+News Items can be read using the eselect command. More information on use
+of this tool to read or delete news items can be found on the news.eselect
+man page.
</p>
</body>
@@ -20,19 +22,44 @@ read or delete news items can be found on the news.eselect man page.
<title>Adding a news item</title>
<body>
-<p>
<ul>
- <li>Choose a file name in the proper format: YYYY-MM-DD-name.lang.txt, where the date is followed by a name (a-z, 0-9, + (plus), - (hyphen) and _ (underscore)), the two-letter ISO language code (en for English must be chosen as default) and the file extension txt.</li>
- <li>Write the news item, which is similar to a RFC-compliant email. Details concerning what is allowed can be found in the appropriate GLEP section. As a note: Exceptions depending on installed packages or activated profiles is possible.</li>
- <li>Send the news item to the gentoo-dev mailing list and the Gentoo PR team (pr@gentoo.org) 72 hours in advance of commit.</li>
- <li>Wait for corrections or feedback that your news item is not of great importance and should be revoked (can be possible).</li>
- <li>Upon acceptance, create a detached armored GnuPG signature with gpg --local-user --detach-sign --armor YYYY-MM-DD-name.lang.txt</li>
- <li>Verify that your signature is correct with gpg --verify YYYY-MM-DD-name.lang.txt.asc YYYY-MM-DD-name.lang.txt</li>
- <li>Create a directory structure for your item in the gentoo-news repository (<c>git+ssh://git@git.gentoo.org/data/gentoo-news.git</c>): YYYY/YYYY-MM-DD-name/.</li>
- <li>Add both the news file and the signature to that directory.</li>
- <li>Commit and push your changes to the gentoo-news repository.</li>
+ <li>
+ Choose a file name in the proper format: YYYY-MM-DD-name.lang.txt,
+ where the date is followed by a name (a-z, 0-9, + (plus), - (hyphen)
+ and _ (underscore)), the two-letter ISO language code (en for English
+ must be chosen as default) and the file extension txt.
+ </li>
+ <li>
+ Write the news item, which is similar to a RFC-compliant email. Details
+ concerning what is allowed can be found in the appropriate GLEP section.
+ As a note: Exceptions depending on installed packages or activated
+ profiles is possible.
+ </li>
+ <li>
+ Send the news item to the gentoo-dev mailing list and the Gentoo PR team
+ (pr@gentoo.org) 72 hours in advance of commit.
+ </li>
+ <li>
+ Wait for corrections or feedback that your news item is not of great
+ importance and should be revoked (can be possible).
+ </li>
+ <li>
+ Upon acceptance, create a detached armored GnuPG signature with
+ gpg --local-user --detach-sign --armor YYYY-MM-DD-name.lang.txt
+ </li>
+ <li>
+ Verify that your signature is correct with
+ gpg --verify YYYY-MM-DD-name.lang.txt.asc YYYY-MM-DD-name.lang.txt
+ </li>
+ <li>
+ Create a directory structure for your item in the gentoo-news repository
+ (<c>git+ssh://git@git.gentoo.org/data/gentoo-news.git</c>):
+ YYYY/YYYY-MM-DD-name/.
+ </li>
+ <li>Add both the news file and the signature to that directory.</li>
+ <li>Commit and push your changes to the gentoo-news repository.</li>
</ul>
-</p>
+
</body>
</section>
next reply other threads:[~2017-11-28 22:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-28 22:52 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-12-22 11:20 [gentoo-commits] proj/devmanual:master commit in: general-concepts/news/ Ulrich Müller
2017-12-21 13:49 Ulrich Müller
2015-08-27 6:50 Justin Lecher
2014-07-24 18:06 Markos Chandras
2014-10-18 17:35 ` Markos Chandras
2012-03-17 10:07 Markos Chandras
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=1511909430.1ca9b99efeabac3522d976ea94caef5b6b227c5d.ulm@gentoo \
--to=ulm@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