From: Mark Harris <mark.hsj@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>
Cc: discuss@mandoc.bsd.lv
Subject: Re: mandoc.css license
Date: Mon, 26 Nov 2018 09:31:31 -0800 [thread overview]
Message-ID: <4d2cd9db-0bc3-6c65-6bc1-736b9bbfcef5@gmail.com> (raw)
In-Reply-To: <20181126171606.GD82448@athene.usta.de>
On 2018-11-26 9:16, Ingo Schwarze wrote:
> But i see how the wording could make people ponder unintended subtleties,
> so i simplified the wording with the commit below.
Thanks! The two commits look good to me.
- Mark
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
prev parent reply other threads:[~2018-11-26 17:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 6:51 Mark Harris
2018-11-26 15:29 ` Ingo Schwarze
2018-11-26 16:43 ` Mark Harris
2018-11-26 17:16 ` Ingo Schwarze
2018-11-26 17:31 ` Mark Harris [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=4d2cd9db-0bc3-6c65-6bc1-736b9bbfcef5@gmail.com \
--to=mark.hsj@gmail.com \
--cc=discuss@mandoc.bsd.lv \
--cc=schwarze@usta.de \
/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).