Просмотр исходного кода

man: Use the feature area name in the subsection title

Using something else is more confusing as it does not match with the
actual feature name.
Guillem Jover лет назад: 11
Родитель
Сommit
e8fedc0a30
2 измененных файлов с 5 добавлено и 4 удалено
  1. 1 0
      debian/changelog
  2. 4 4
      man/dpkg-buildflags.1

+ 1 - 0
debian/changelog

@@ -5,6 +5,7 @@ dpkg (1.18.2) UNRELEASED; urgency=low
   * Documentation:
   * Documentation:
     - Fix grammar in dpkg-architecture(1).
     - Fix grammar in dpkg-architecture(1).
       Thanks to Chris Lamb <lamby@debian.org>. Closes: #787616
       Thanks to Chris Lamb <lamby@debian.org>. Closes: #787616
+    - Use the feature area name in the dpkg-buildflags(1) subsection title.
 
 
   [ Updated programs translations ]
   [ Updated programs translations ]
   * Dutch (Frans Spiesschaert). Closes: #789097
   * Dutch (Frans Spiesschaert). Closes: #789097

+ 4 - 4
man/dpkg-buildflags.1

@@ -215,7 +215,7 @@ Thus disabling everything in the \fBhardening\fP area and enabling only
 .P
 .P
   export DEB_BUILD_MAINT_OPTIONS=hardening=\-all,+format,+fortify
   export DEB_BUILD_MAINT_OPTIONS=hardening=\-all,+format,+fortify
 .
 .
-.SS Quality Assurance (QA)
+.SS qa
 Several compile-time options (detailed below) can be used to help detect
 Several compile-time options (detailed below) can be used to help detect
 problems in the source code or build system.
 problems in the source code or build system.
 .TP
 .TP
@@ -232,7 +232,7 @@ The only currently supported flags are \fBCPPFLAGS\fP, \fBCFLAGS\fP,
 to \fB\-D__DEB_CANARY_\fP\fIflag\fP_\fIrandom-id\fP\fB__\fP, and
 to \fB\-D__DEB_CANARY_\fP\fIflag\fP_\fIrandom-id\fP\fB__\fP, and
 \fBLDFLAGS\fP set to \fB\-Wl,\-z,deb-canary\-\fP\fIrandom-id\fP.
 \fBLDFLAGS\fP set to \fB\-Wl,\-z,deb-canary\-\fP\fIrandom-id\fP.
 .
 .
-.SS Sanitize
+.SS sanitize
 Several compile-time options (detailed below) can be used to help sanitize
 Several compile-time options (detailed below) can be used to help sanitize
 a resulting binary against memory corruptions, memory leaks, use after free,
 a resulting binary against memory corruptions, memory leaks, use after free,
 threading data races and undefined behavior bugs.
 threading data races and undefined behavior bugs.
@@ -254,7 +254,7 @@ or the \fBthread\fP features are enabled, as they imply it.
 .B undefined
 .B undefined
 This setting (disabled by default) adds \fB\-fsanitize=undefined\fP to
 This setting (disabled by default) adds \fB\-fsanitize=undefined\fP to
 \fBCFLAGS\fP, \fBCXXFLAGS\fP and \fBLDFLAGS\fP.
 \fBCFLAGS\fP, \fBCXXFLAGS\fP and \fBLDFLAGS\fP.
-.SS Hardening
+.SS hardening
 Several compile-time options (detailed below) can be used to help harden
 Several compile-time options (detailed below) can be used to help harden
 a resulting binary against memory corruption attacks, or provide
 a resulting binary against memory corruption attacks, or provide
 additional warning messages during compilation.
 additional warning messages during compilation.
@@ -362,7 +362,7 @@ architectures (most notably i386) can see performance losses of up to
 15% in very text-segment-heavy application workloads; most workloads
 15% in very text-segment-heavy application workloads; most workloads
 see less than 1%. Architectures with more general registers (e.g. amd64)
 see less than 1%. Architectures with more general registers (e.g. amd64)
 do not see as high a worst-case penalty.
 do not see as high a worst-case penalty.
-.SS Reproducibility
+.SS reproducible
 The compile-time options detailed below can be used to help improve
 The compile-time options detailed below can be used to help improve
 build reproducibility or provide additional warning messages during
 build reproducibility or provide additional warning messages during
 compilation. Except as noted below, these are enabled by default for
 compilation. Except as noted below, these are enabled by default for