From: bugzilla-daemon@kernel.org
To: linux-man@vger.kernel.org
Subject: [Bug 220726] Patch of ioctl_vt (2), small clarification.
Date: Sat, 13 Dec 2025 15:41:26 +0000 [thread overview]
Message-ID: <bug-220726-11311-7VQ8DFQKuZ@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 #7 from Alejandro Colomar (alx@kernel.org) ---
Hi Teika,
On Sat, Dec 13, 2025 at 08:00:04AM +0000, bugzilla-daemon@kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=220726
>
> teika kazura (teika@gmx.com) changed:
>
> What |Removed |Added
> ----------------------------------------------------------------------------
> Attachment #308874|0 |1
> is obsolete| |
>
> --- Comment #6 from teika kazura (teika@gmx.com) ---
> Created attachment 309016
> --> https://bugzilla.kernel.org/attachment.cgi?id=309016&action=edit
> My version of vt_ioctl.2
>
> This is the third version of vt_ioctl.2. Unlike preceding versions this is
> not
> a patch, but the entire file. The second version was posted to the mailing
> list:
>
> <https://lore.kernel.org/linux-man/20251110.165618.2111633615163528521.teika@gmx.com/T/#u>.
> The accuracy was justified in the post cited above (and follow up emails.)
>
> My contribution is released to the public domain. I don't post the
> corresponding patch, but it is based on the git HEAD as of today, i.e.
>
> <https://git.kernel.org/pub/scm/docs/man-pages/man-pages.git/commit/man/man2/ioctl_vt.2?id=9fbe82>.
>
> The project refuses my work to merge because of not complying with its policy
> about the use of AIs. I believe my improvement helps, so hereby post for the
> community's sake.
We don't refuse to take your work. You seem to refuse to follow our
policies. You're welcome to do work that is clean of AI, and we'll
consider it. But AI-derived code will not be accepted anywhere in this
project, including the bugzilla. I've marked the attachment as private.
Have a lovely day!
Alex
>
> Best regards.
--
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-13 15: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 [this message]
2025-12-15 5:41 ` bugzilla-daemon
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-7VQ8DFQKuZ@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.