linux-kernel - Re: Commit Links [was: Linux 6.17-rc5]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20250912191400.GA39973@ZenIV>
Date: Fri, 12 Sep 2025 20:14:00 +0100
From: Al Viro <viro@...iv.linux.org.uk>
To: Jiri Slaby <jirislaby@...nel.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Commit Links [was: Linux 6.17-rc5]

On Fri, Sep 12, 2025 at 08:24:06AM +0200, Jiri Slaby wrote:

> OK, can we have Submitted-at: or something for the above which you could
> completely ignore?

Sigh...  Same question: what am I supposed to do when posting a branch
for review?  The only answer I've heard so far had been "well, you could
discard that branch later and apply what you'd posted [git format-patch
output, that is] via git am or something similar to it", which is more
than slightly ridiculous.

IDGI...