discuss@mandoc.bsd.lv
 help / color / mirror / Atom feed
From: Kristaps Dzonsons <kristaps@bsd.lv>
To: "discuss@mdocml.bsd.lv" <discuss@mdocml.bsd.lv>
Subject: Re: FreeBSD + mandoc (GSoC)
Date: Fri, 28 May 2010 16:06:48 +0200	[thread overview]
Message-ID: <4BFFCDF8.6020602@bsd.lv> (raw)
In-Reply-To: <AANLkTiny4fFLqUUEMhJGHfk2d9iYFgYruxEqOaK6j97H@mail.gmail.com>

> I'm working on moving mandoc ports to FreeBSD base. Ulrich has informed
> me of related work he's already started; I just wanted to get this list
> notified as well.
> 
> Original posting to freebsd-hackers (and several responses) here:
> http://lists.freebsd.org/pipermail/freebsd-hackers/2010-May/031892.htmll

Ben,

Welcome!

When the next release hits (Real Soon Now), the web-site will be updated
with the new mailing lists, which I suggest you subscribe to.

The responses in that thread seem like the same tired arguments, but if
FreeBSD has a lot of roff stuff lying around, and speed, documentation,
regularity, etc. aren't really regarded, then that's how it goes.

Unless they want to play with GPLv3, which is groff's new license,
they're going to have to use either plan9 or heirloom.  I know heirloom
hasn't updated their -mdoc package since 4.4BSD.  As for the former:

http://swtch.com/usr/local/plan9/tmac/

Note no "tmac.doc".  That's going to be fun!

Take care,

Kristaps
--
 To unsubscribe send an email to discuss+unsubscribe@mdocml.bsd.lv

      parent reply	other threads:[~2010-05-28 13:57 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-27 12:54 Ben Fiedler
2010-05-27 13:08 ` Ingo Schwarze
2010-05-27 13:13 ` Ulrich Spörlein
2010-05-28 14:06 ` Kristaps Dzonsons [this message]

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=4BFFCDF8.6020602@bsd.lv \
    --to=kristaps@bsd.lv \
    --cc=discuss@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).