Bug#921306: dgit.1: Use a single-font-style macro for a single argument

2019-03-01 Thread Ian Jackson
Bjarni Ingi Gislason writes ("Bug#921306: dgit.1: Use a single-font-style macro 
for a single argument"):
> Package: dgit
> Version: 8.3
> Severity: minor
> Tags: patch
...
>   Use a single-font-style macro (".B", ".I") for a single argument.
>   Remove unneeded quotation marks (").
>   The output from "nroff" and "groff" is unchanged with this patch.

Hi.  Thanks for your contribution.  However, I don't see the value, I
am afraid.  In general where I use .BI "unnecessarily" I do it where
it is likely that I might want to use .BI in the future.  So this is
likely to make future changes difficult.

So I won't be applying this patch, at least unless you would care to
present a reason why it is beneficial other than simple tidiness.

Regards,
Ian.



Bug#921306: dgit.1: Use a single-font-style macro for a single argument

2019-02-03 Thread Bjarni Ingi Gislason
Package: dgit
Version: 8.3
Severity: minor
Tags: patch

Dear Maintainer,

>From b706387a72d95ae30652901f126f92be90699b28 Mon Sep 17 00:00:00 2001
>Date: Mon, 4 Feb 2019 02:30:04 +

  Use a single-font-style macro (".B", ".I") for a single argument.

  Remove unneeded quotation marks (").

  The output from "nroff" and "groff" is unchanged with this patch.

  [ There are still some typographical mistakes left. ]

Signed-off-by: Bjarni Ingi Gislason 
---
 dgit.1 | 64 +-
 1 file changed, 32 insertions(+), 32 deletions(-)

diff --git a/dgit.1 b/dgit.1
index 6f89574..f0d2a8f 100644
--- a/dgit.1
+++ b/dgit.1
@@ -462,12 +462,12 @@ Prints version information and exits.
 Tries to fetch a copy of the source code for the dgit-repos-server,
 as actually being used on the dgit git server, as a git tree.
 .TP
-.BI "dgit print-dgit-repos-server-source-url"
+.B dgit print-dgit-repos-server-source-url
 Prints the url used by dgit clone-dgit-repos-server.
 This is hopefully suitable for use as a git remote url.
 It may not be useable in a browser.
 .TP
-.BI "dgit print-dpkg-source-ignores"
+.B dgit print-dpkg-source-ignores
 Prints the -i and -I arguments which must be passed to dpkg-souce
 to cause it to exclude exactly the .git directory
 and nothing else.
@@ -515,7 +515,7 @@ distro's
 config setting (see CONFIGURATION, below), or failing that, the
 uploader trailer line in debian/changelog.
 .TP
-.BR --no-sign
+.B --no-sign
 does not sign tags or uploads (meaningful only with push).
 .TP
 .TP
@@ -527,7 +527,7 @@ Valid with dgit fetch and dgit pull, only.
 .TP
 .BR --clean=git " | " -wg
 Use
-.BR "git clean -xdf"
+.B git clean -xdf
 to clean the working tree,
 rather than running the package's rules clean target.
 
@@ -548,7 +548,7 @@ See --clean=git[-ff],always, below.
 .TP
 .BR --clean=git-ff " | " -wgf
 Use
-.BR "git clean -xdff"
+.B git clean -xdff
 to clean the working tree.
 Like
 git clean -xdf
@@ -566,7 +566,7 @@ Avoids running rules clean,
 and can avoid needing the build-dependencies.
 
 With
-.BR ,ignores
+.B ,ignores
 or
 .BR -wci ,
 untracked files covered by .gitignore are tolerated,
@@ -599,7 +599,7 @@ or
 .BR -wdd ,
 the build-dependencies are not checked
 (due to passing
-.BR -d
+.B -d
 to dpkg-buildpackage),
 which violates policy, but may work in practice.
 
@@ -635,7 +635,7 @@ refuse to push.  It may (for Debian, will) be unable to 
access the git
 history for any packages which have been newly pushed and have not yet
 been published.
 .TP
-.BR --include-dirty
+.B --include-dirty
 Do not complain if the working tree does not match your git HEAD,
 and when building,
 include the changes from your working tree.
@@ -643,7 +643,7 @@ This can be useful with build, if you plan to commit later. 
 (dgit
 push will still ensure that the .dsc you upload and the git tree
 you push are identical, so this option won't make broken pushes.)
 .TP
-.BR --ignore-dirty
+.B --ignore-dirty
 Deprecated alias for --include-dirty.
 .TP
 .BR --overwrite [=\fIprevious-version\fR]
@@ -685,7 +685,7 @@ changes, even with
 unless someone committed to git a finalised changelog
 entry, and then made later changes to that version.)
 If
-.IR previous-version
+.I previous-version
 is specified, it ought to be the version currently in the archive.
 
 dgit push --overwrite
@@ -717,7 +717,7 @@ someone should make a suitable dgit push
 to update the contents of dgit-repos
 to a version without the controversial changes.
 .TP
-.BR --no-chase-dsc-distro
+.B --no-chase-dsc-distro
 Tells dgit not to look online
 for additional git repositories
 containing information about a particular .dsc being imported.
@@ -780,7 +780,7 @@ The meanings of
 .IR something s
 understood in the context of Debian are discussed below:
 .TP
-.BR --deliberately-not-fast-forward
+.B --deliberately-not-fast-forward
 Declare that you are deliberately rewinding history.  When pushing to
 Debian, use this when you are making a renewed upload of an entirely
 new source package whose previous version was not accepted for release
@@ -797,7 +797,7 @@ and
 should be needed;
 --overwrite is usually better.
 .TP
-.BR --deliberately-include-questionable-history
+.B --deliberately-include-questionable-history
 Declare that you are deliberately including, in the git history of
 your current push, history which contains a previously-submitted
 version of this package which was not approved (or has not yet been
@@ -806,12 +806,12 @@ option after verifying that: none of the 
rejected-from-NEW (or
 never-accepted) versions in the git history of your current push, were
 rejected by ftpmaster for copyright or redistributability reasons.
 .TP
-.BR --deliberately-fresh-repo
+.B --deliberately-fresh-repo
 Declare that you are deliberately rewinding history and want to
 throw away the existing repo.  Not relevant when pushing to Debian,
 as the Debian server will do this automatically when necessary.
 .TP
-.BR --quilt=linear
+.B