From: schwarze@mandoc.bsd.lv
To: source@mandoc.bsd.lv
Subject: mandoc: delete the entry for a crash that was already fixed
Date: Sun, 19 Jan 2020 11:28:13 -0500 (EST) [thread overview]
Message-ID: <ba40bb70d238d7f0@mandoc.bsd.lv> (raw)
Log Message:
-----------
delete the entry for a crash that was already fixed
Modified Files:
--------------
mandoc:
TODO
Revision Data
-------------
Index: TODO
===================================================================
RCS file: /home/cvs/mandoc/mandoc/TODO,v
retrieving revision 1.299
retrieving revision 1.300
diff -LTODO -LTODO -u -p -r1.299 -r1.300
--- TODO
+++ TODO
@@ -33,14 +33,6 @@ Obviously, as the issues have not been s
are mere guesses, and some may be wrong.
************************************************************************
-* crashes
-************************************************************************
-
-- .ce .if n .B two crashes because "return (*roffs[t].sub)" bypasses
- the "high level macros abort .ce" safeguard in roff_parseln()
- reported by espie@ in textproc/fstrcmp
-
-************************************************************************
* missing features
************************************************************************
--
To unsubscribe send an email to source+unsubscribe@mandoc.bsd.lv
reply other threads:[~2020-01-19 16:28 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ba40bb70d238d7f0@mandoc.bsd.lv \
--to=schwarze@mandoc.bsd.lv \
--cc=source@mandoc.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).