From: schwarze@mdocml.bsd.lv
To: source@mdocml.bsd.lv
Subject: mdocml: fix build when HAVE_MANPATH is set; patch from <bapt at FreeBSD>
Date: Wed, 26 Nov 2014 19:30:40 -0500 (EST) [thread overview]
Message-ID: <7148290920393875860.enqueue@fantadrom.bsd.lv> (raw)
Log Message:
-----------
fix build when HAVE_MANPATH is set; patch from <bapt at FreeBSD>
Modified Files:
--------------
mdocml:
manpath.c
Revision Data
-------------
Index: manpath.c
===================================================================
RCS file: /home/cvs/mdocml/mdocml/manpath.c,v
retrieving revision 1.18
retrieving revision 1.19
diff -Lmanpath.c -Lmanpath.c -u -p -r1.18 -r1.19
--- manpath.c
+++ manpath.c
@@ -80,7 +80,7 @@ manpath_parse(struct manpaths *dirs, con
if ( ! ferror(stream) && feof(stream) &&
bsz && '\n' == buf[bsz - 1]) {
buf[bsz - 1] = '\0';
- manpath_parseline(dirs, buf);
+ manpath_parseline(dirs, buf, 1);
}
free(buf);
--
To unsubscribe send an email to source+unsubscribe@mdocml.bsd.lv
reply other threads:[~2014-11-27 0:30 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=7148290920393875860.enqueue@fantadrom.bsd.lv \
--to=schwarze@mdocml.bsd.lv \
--cc=source@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).