From: Greg Kroah-Hartman via Libc-alpha <libc-alpha@sourceware.org>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: "Marek Behún" <kabel@kernel.org>,
linux-man@vger.kernel.org, libc-alpha@sourceware.org,
"Michael Kerrisk" <mtk.manpages@gmail.com>,
linux-serial@vger.kernel.org,
"G. Branden Robinson" <g.branden.robinson@gmail.com>,
"Pali Rohár" <pali@kernel.org>
Subject: Re: [PATCH v3] ioctl_tty.2: Add example how to get or set baudrate on the serial port
Date: Thu, 5 Aug 2021 18:14:33 +0200 [thread overview]
Message-ID: <YQwOaWqbHFG29wQF@kroah.com> (raw)
In-Reply-To: <418a281b-441d-66fc-6929-5d29fafc459b@gmail.com>
On Thu, Aug 05, 2021 at 05:28:49PM +0200, Alejandro Colomar (man-pages) wrote:
> Hi Pali,
>
> On 8/5/21 11:51 AM, Pali Rohár wrote:
> > > > > Also, you forgot a license for this code, that is required if you want
> > > > > people to use it...
> > > >
> > > > Hm... I do not see any license in other manpage examples. Does not apply
> > > > for it global license defined in ioctl_tty.2 file?
> > >
> > > That does not mean you do not need it.
>
> I don't know what is the status of the current code examples in terms of
> licensing.
>
> I thought I had seen an SPDX license identifier in one of them some time
> ago, but now I can't find it.
>
> Technically, the pages have a license at the top of each file, which isn't
> printed on the rendered output (the license text doesn't require so) (see
> that text below).
>
> If you want a different license for your example (let's say you want it BSD
> for example), I guess you could add an SPDX line at the top of the example
> for simplicity.
>
> But if your code example adheres to the same license as the rest of the
> page, I guess you don't need to do anything in your patch.
What is the license of a man page?
What is the license of this page?
And if it is not shown in the code segment itself, that's going to be a
mess, please make it explicit, otherwise no one can ever use any of the
code examples for anything.
thanks,
greg k-h
next prev parent reply other threads:[~2021-08-05 16:15 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-30 9:53 [PATCH] ioctl_tty.2: Add example how to get or set baudrate on the serial port Pali Rohár via Libc-alpha
2021-07-30 11:47 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-07-30 12:05 ` Pali Rohár via Libc-alpha
2021-07-30 12:21 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-07-30 13:02 ` [PATCH v2] " Pali Rohár via Libc-alpha
2021-08-01 13:51 ` [PATCH v3] " Pali Rohár via Libc-alpha
2021-08-04 22:08 ` Pali Rohár via Libc-alpha
2021-08-05 5:52 ` Greg Kroah-Hartman via Libc-alpha
2021-08-05 8:22 ` Pali Rohár via Libc-alpha
2021-08-05 8:30 ` Greg Kroah-Hartman via Libc-alpha
2021-08-05 8:44 ` Pali Rohár via Libc-alpha
2021-08-05 8:50 ` Greg Kroah-Hartman via Libc-alpha
2021-08-05 9:51 ` Pali Rohár via Libc-alpha
2021-08-05 15:28 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-08-05 16:14 ` Greg Kroah-Hartman via Libc-alpha [this message]
2021-08-05 16:45 ` Licensing example programs in man-pages (was [PATCH v3] ioctl_tty.2: Add example how to get or set baudrate on the serial port) Alejandro Colomar (man-pages) via Libc-alpha
2021-08-05 17:54 ` Greg Kroah-Hartman via Libc-alpha
2021-08-06 7:22 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-08-06 8:32 ` Pali Rohár via Libc-alpha
2021-08-08 8:35 ` [PATCH v3] ioctl_tty.2: Add example how to get or set baudrate on the serial port Alejandro Colomar (man-pages) via Libc-alpha
2021-08-08 21:05 ` Pali Rohár via Libc-alpha
2021-08-08 21:19 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-08-10 19:49 ` [PATCH v4] " Pali Rohár via Libc-alpha
2021-08-10 20:11 ` Pali Rohár via Libc-alpha
2021-08-31 20:34 ` Pali Rohár via Libc-alpha
2021-09-10 13:37 ` Alejandro Colomar (man-pages) via Libc-alpha
2021-09-10 13:39 ` Pali Rohár via Libc-alpha
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YQwOaWqbHFG29wQF@kroah.com \
--to=libc-alpha@sourceware.org \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=kabel@kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
--cc=pali@kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).