[latex3-commits] [git/LaTeX3-latex3-latex2e] gh479: This is all in the documentation, so make ltnews simpler (02e0ed9a)

[PhelypeOleinik]

Repository : https://github.com/latex3/latex2e
On branch  : gh479
Link       : https://github.com/latex3/latex2e/commit/02e0ed9a02168a60ef0106b7ce49c3672fa84777

>---------------------------------------------------------------

commit 02e0ed9a02168a60ef0106b7ce49c3672fa84777
Author: PhelypeOleinik <phelype.oleinik at latex-project.org>
Date:   Sat Mar 20 09:41:38 2021 -0300

    This is all in the documentation, so make ltnews simpler


>---------------------------------------------------------------

02e0ed9a02168a60ef0106b7ce49c3672fa84777
 base/doc/ltnews33.tex | 13 +++----------
 1 file changed, 3 insertions(+), 10 deletions(-)

diff --git a/base/doc/ltnews33.tex b/base/doc/ltnews33.tex
index 1a16fefc..c86d8658 100644
--- a/base/doc/ltnews33.tex
+++ b/base/doc/ltnews33.tex
@@ -477,16 +477,9 @@ and that would result in errors, as usual with commands defined with
 \cs{newcommand} or in the case of \pkg{lthooks}, \cs{cs\_new:Npn}.
 
 To solve this issue, now completely new modules can be defined in
-\pkg{latexrelease} using two new commands:
-\begin{quote}
-\cs{NewModuleRelease}\verb|{|\meta{name}\verb|}{|\meta{release date}\verb|}|\\
-\null\quad\meta{module code}\\
-\cs{EndModuleRelease}
-\end{quote}
-and then when rolling back or forward \pkg{latexrelease} will know if the code
-of the module has to be read or completely ignored. Additionally, changes to
-such module can still be declared with the well-known \cs{IncludeInRelease}
-command, and these changes will be applied accordingly.  More details can be
+\pkg{latexrelease} using \cs{NewModuleRelease}
+and then when rolling back or forward it will know if the code
+of the module has to be read or completely ignored.  More details can be
 found in the \pkg{latexrelease} documentation (\verb|texdoc latexrelease|).
 %
 \githubissue{479}