From: Mark Harris <mark.hsj@gmail.com>
To: discuss@mandoc.bsd.lv
Subject: mandoc.css license
Date: Sun, 25 Nov 2018 22:51:35 -0800 [thread overview]
Message-ID: <923c3207-224b-0345-3215-8f457d613cd1@gmail.com> (raw)
It appears that it is intended that the mandoc.css file included with
mandoc be served as a static file from any web server that is serving
mandoc-generated html. If this file is BSD licensed, should it have a
copyright notice and copy of the BSD license at the top so that it can
be distributed separately? Or does it not require this because CSS is
not considered to be code or documentation? Would it be possible to
clarify the status of this file in the LICENSE file and/or in a comment
at the beginning of mandoc.css?
Thanks,
- Mark
--
To unsubscribe send an email to discuss+unsubscribe@mandoc.bsd.lv
next reply other threads:[~2018-11-26 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-26 6:51 Mark Harris [this message]
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
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=923c3207-224b-0345-3215-8f457d613cd1@gmail.com \
--to=mark.hsj@gmail.com \
--cc=discuss@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).