commit:     969156f60e46ca8fd299c38483a42f9776047a1c
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Aug  1 02:53:35 2021 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sat Aug 14 01:46:15 2021 +0000
URL:        https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=969156f6

ebuild-writing/file-format: rewrap long paragraph

Signed-off-by: Sam James <sam <AT> gentoo.org>
Closes: https://github.com/gentoo/devmanual/pull/242
Signed-off-by: Sam James <sam <AT> gentoo.org>

 ebuild-writing/file-format/text.xml | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/ebuild-writing/file-format/text.xml 
b/ebuild-writing/file-format/text.xml
index d9b0758..0065b22 100644
--- a/ebuild-writing/file-format/text.xml
+++ b/ebuild-writing/file-format/text.xml
@@ -135,11 +135,12 @@ algorithm</uri> can be found in PMS.
 <body>
 
 <p>
-When packaging a snapshot of a source repository, there are two commonly used 
formats. The first
-treats the snapshot as a patch to the previous version, and so the ebuild 
version is in the format
-$(last-released-version)_pYYYYMMDD. Alternatively, the snapshot may be treated 
as a pre-release to
-an upcoming version, usually used when a release is anticipated but not out 
yet. The format for this
-is $(upcoming-version)_preYYYYMMDD.
+When packaging a snapshot of a source repository, there are two commonly used
+formats. The first treats the snapshot as a patch to the previous version, and
+so the ebuild version is in the format $(last-released-version)_pYYYYMMDD.
+Alternatively, the snapshot may be treated as a pre-release to an upcoming
+version, usually used when a release is anticipated but not out yet. The format
+for this is $(upcoming-version)_preYYYYMMDD.
 </p>
 
 <p>

Reply via email to