linux-kernel - Re: [PATCH v11 0/8] Rust support for mm_struct, vm_area

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: <CAH5fLggpBTZ7E4M5W7fN928z82_+zpD3kpvxinG9nfsu07Wkuw@mail.gmail.com>
Date: Fri, 13 Dec 2024 15:42:48 +0100
From: Alice Ryhl <aliceryhl@...gle.com>
To: Konstantin Ryabitsev <konstantin@...uxfoundation.org>
Cc: linux-kernel@...r.kernel.org, linux-mm@...ck.org, 
	rust-for-linux@...r.kernel.org
Subject: Re: [PATCH v11 0/8] Rust support for mm_struct, vm_area_struct, and mmap

On Thu, Dec 12, 2024 at 3:47 PM Konstantin Ryabitsev
<konstantin@...uxfoundation.org> wrote:
>
> On Wed, Dec 11, 2024 at 11:47:41AM +0100, Alice Ryhl wrote:
> > When I sent this series, b4 put the changelog stub for v12 above the
> > cover letter for some reason. Also, I'm not sure why the list of
> > recipients were included in the cover letter. Any ideas what I'm doing
> > wrong?
>
> Yes, and it's a common gotcha that I don't know how to properly address. For
> the moment, we use "---" lines to indicate the main sections of the cover
> letter. There are three main sections:
>
>     The main message
>
>     ---
>
>     Additional information
>
>     ---
>
>     The basement
>
> Looks like you removed the "---" between the changelog and the main message,
> which causes b4 to stop properly parsing the cover letter.
>
> I'm open to suggestions on how to make this less fragile, short of "use AI to
> figure out what part of the cover letter does what."

Could you print an error if the --- is missing, that is, if the number
of sections is incorrect?

Alice