linux-kernel - Re: [PATCH] docs: submitting-patches: improve the base commit explanation

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: <202311150948.F6E39AD@keescook>
Date:   Wed, 15 Nov 2023 09:49:31 -0800
From:   Kees Cook <keescook@...omium.org>
To:     Borislav Petkov <bp@...en8.de>
Cc:     Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
        linux-doc@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] docs: submitting-patches: improve the base commit
 explanation

On Wed, Nov 15, 2023 at 06:03:30PM +0100, Borislav Petkov wrote:
> From: "Borislav Petkov (AMD)" <bp@...en8.de>
> 
> After receiving a second patchset this week without knowing which tree
> it applies on and trying to apply it on the obvious ones and failing,
> make sure the base tree information which needs to be supplied in the
> 0th message of the patchset is spelled out more explicitly.
> 
> Also, make the formulations stronger as this really is a requirement and
> not only a useful thing anymore.
> 
> Signed-off-by: Borislav Petkov (AMD) <bp@...en8.de>

Yup, I wonder if making "--base=auto" a default in git might be a good
idea too?

Reviewed-by: Kees Cook <keescook@...omium.org>

-- 
Kees Cook