diff options
| author |   Ulrich Müller <ulm@gentoo.org> | 2021-04-25 23:20:55 +0200 |
|---|---|---|
| committer | Ulrich Müller <ulm@gentoo.org> | 2021-04-30 18:24:30 +0200 |
| commit | 54330c67cb6374e0bd704ea775871161ba7fdf72 (patch) | |
| tree | 5549350aa5baaf6f407128148340890ae1022b04 /introduction.tex | |
| parent | pms.tex: Update copyright years (diff) | |
| download | pms-54330c67cb6374e0bd704ea775871161ba7fdf72.tar.gz pms-54330c67cb6374e0bd704ea775871161ba7fdf72.tar.bz2 pms-54330c67cb6374e0bd704ea775871161ba7fdf72.zip | |
pms.cls: Do not define \e for \emph
This is only used a few times, so a shorthand is not needed.
(We really should get rid of \i and \t as well, because redefining
LaTeX internal commands sucks.)
Signed-off-by: Ulrich Müller <ulm@gentoo.org>
Diffstat (limited to 'introduction.tex')
| -rw-r--r-- | introduction.tex | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/introduction.tex b/introduction.tex index 8d1f793..b72acc3 100644 --- a/introduction.tex +++ b/introduction.tex @@ -5,7 +5,7 @@ This document aims to fully describe the format of an ebuild repository and the ebuilds therein, as well as certain aspects of package manager behaviour required to support such a repository. -This document is \e{not} designed to be an introduction to ebuild development. Prior knowledge of +This document is \emph{not} designed to be an introduction to ebuild development. Prior knowledge of ebuild creation and an understanding of how the package management system works is assumed; certain less familiar terms are explained in the Glossary in chapter~\ref{ch:glossary}. @@ -28,7 +28,7 @@ incompatibilities with any particular repository. \section{Reporting Issues} Issues (inaccuracies, wording problems, omissions etc.)\ in this document should be reported via -Gentoo Bugzilla using product \e{Gentoo Hosted Projects}, component \e{PMS/EAPI} and the default +Gentoo Bugzilla using product \i{Gentoo Hosted Projects}, component \i{PMS/EAPI} and the default assignee. There should be one bug per issue, and one issue per bug. Patches (in \t{git format-patch} form if possible) may be submitted either via Bugzilla or to the |