From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 220726] Patch of ioctl_vt (2), small clarification.
Date: Mon, 15 Dec 2025 05:41:51 +0000 [thread overview]
Message-ID: <bug-220726-11311-epnxiInr8d@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220726-11311@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220726
--- Comment #8 from teika kazura (teika@gmx.com) ---
Hi. Hiding my last post here is wrong, because mine was done outside the
man-pages project. Manual pages are GPL'd and anyone can do anything as long as
they obey the license. You don't have the right to do it. Everyone mistakes and
that's ok, but lift it.
Also remember kernel bugzilla is not only for man-pages, and at least the
kernel itself does not have any policy about the AI use. I know my post does
not directly help any projects hosted here right now, but I'm not spamming
either.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2025-12-15 5:41 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 4:41 [Bug 220726] New: Patch of ioctl_vt (2), small clarification bugzilla-daemon
2025-10-31 9:45 ` [Bug 220726] " bugzilla-daemon
2025-11-10 7:30 ` bugzilla-daemon
2025-11-10 10:11 ` Alejandro Colomar
2025-11-10 7:32 ` bugzilla-daemon
2025-11-10 7:32 ` bugzilla-daemon
2025-11-10 10:11 ` bugzilla-daemon
2025-12-13 8:00 ` bugzilla-daemon
2025-12-13 15:36 ` bugzilla-daemon
2025-12-13 15:37 ` bugzilla-daemon
2025-12-13 15:41 ` bugzilla-daemon
2025-12-15 5:41 ` bugzilla-daemon [this message]
2025-12-15 10:20 ` bugzilla-daemon
2025-12-15 11:52 ` bugzilla-daemon
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=bug-220726-11311-epnxiInr8d@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@kernel.org \
--cc=linux-man@vger.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