git: 5537773877 - main - Trim trailing white spaces

Li-Wen Hsu <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
The branch main has been updated by lwhsu:

URL: https://cgit.FreeBSD.org/doc/commit/?id=5537773877c04407052806a15e32587702438734

commit 5537773877c04407052806a15e32587702438734
Author:     Li-Wen Hsu <[email protected]>
AuthorDate: 2023-09-03 15:04:17 +0000
Commit:     Li-Wen Hsu <[email protected]>
CommitDate: 2023-09-03 15:04:17 +0000

    Trim trailing white spaces
    
    Sponsored by:   The FreeBSD Foundation
---
 shared/releases.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/shared/releases.adoc b/shared/releases.adoc
index 049655bb2a..b913b33bbc 100644
--- a/shared/releases.adoc
+++ b/shared/releases.adoc
@@ -3,17 +3,17 @@
 // create some links on web sites and such, so do NOT change it until
 // it's really release time.  When you update this, you should also
 // update (at least) the following:
-// 
+//
 // -similar entity in the Handbook
 // -similar entity in the Relnotes
 // -releases/index.adoc has the date of the current release
 // -the FAQ has links to the release FTP url
 // -"versions supported" in security.adoc
-// 
+//
 // (If you're the release engineer, feel free to update this list with
 // other doc-related things you had to do.  It'll save you time and
 // trouble the next time around :-).)
-// 
+//
 // As of 5.0, we now have the concept of two different "currently"
 // released versions (from two different development branches).  Use
 // rel.* and u-rel-* for the "latest and greatest" version and
@@ -49,7 +49,7 @@
 
 // If we have a second release in the release cycle (e.g. 5.x and 6.y
 // are having release candidates at the same time), do the same here.
-      
+
 // Set to 'INCLUDE' when the schedule is available.
 
 :beta2-upcoming: IGNORE
@@ -77,7 +77,7 @@
 // sweep.  This allows switching rel.current, rel1.current, and
 // rel2.current versions below with updated macros here, ultimately
 // touching as few files as necessary.
-// 
+//
 // Note, this is a first pass at this structure, and by no means
 // fully complete yet.  I plan to followup on this and expand it
 // more (in addition to cleaning up this file) following the 11.3
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.