tech@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Ingo Schwarze <schwarze@usta.de>
To: tech@mdocml.bsd.lv
Subject: sync results
Date: Tue, 5 Jul 2011 00:45:19 +0200	[thread overview]
Message-ID: <20110704224519.GC28684@iris.usta.de> (raw)

Hi Kristaps,

i'm currently syncing from bsd.lv to openbsd.org.
The code looks good, and in the output, i see many improvements,
so i will now commit the sync.


However, there are also a three tiny regressions:

cvs(1) contains this code:

.TP 1i
\fB?\fP \fIfile\fP
\fIfile\fP is in your working directory, but does not correspond to
anything in the source repository, and is not in the list of files
for \fBcvs\fP to ignore (see the description of the \fB\-I\fP option).
.PP
.RS .5i
.sp
Use the
.B \-A
option to reset any sticky tags, dates, or
.B \-k
options.  (If you get a working copy of a file by using one of the

Now doubtless, .PP .RS .sp in a row is horrible.
However, with groff and old mandoc, that gave one blank line.
Now there are two.


lynx(1) contains this code:

.TP
.B \-cookie_file\fR=\fIFILENAME
specifies a file to use to read cookies.

In groff and old mandoc, the indent of "specifies" relative to "-cookie"
was 7, now it is 5.


nsd-xfer(8) contains this code:

.SH "OPTIONS"
.LP 
.TP
.B \-4
Only send to IPv4 addresses.

In groff and old mandoc, there is no blank line after OPTIONS,
now there is one.


Note this is the first time that i managed to use the whole OpenBSD
base tree (3725 distinct pages) for doing regression checks after a
merge, and the above is all i found.

Yours,
  Ingo
--
 To unsubscribe send an email to tech+unsubscribe@mdocml.bsd.lv

             reply	other threads:[~2011-07-04 22:45 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-04 22:45 Ingo Schwarze [this message]
2011-07-05 12:43 ` Kristaps Dzonsons
2011-07-05 14:06   ` Kristaps Dzonsons
2011-07-07  4:13     ` Ingo Schwarze
2011-07-06  6:03   ` Ingo Schwarze
2011-07-07 10:27     ` Kristaps Dzonsons
2011-07-07 21:11       ` Ingo Schwarze

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110704224519.GC28684@iris.usta.de \
    --to=schwarze@usta.de \
    --cc=tech@mdocml.bsd.lv \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).