Re: [PATCH v4 1/1] printk: fix zero-valued printk timestamps in early boot

[David Laight <david.laight.linux@gmail.com>]

On Thu, 16 Apr 2026 11:38:53 +0200
"Roberto A. Foglietta" <roberto.foglietta@gmail.com> wrote:

> On Thu, 16 Apr 2026 at 10:44, Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> >
> > Hi Roberto,
> >
> > On Thu, 16 Apr 2026 at 10:25, Roberto A. Foglietta
> > <roberto.foglietta@gmail.com> wrote:  
> > > In attachment the V6 of the patch, and these are the changes since Tim
> > > proposed it:  
> >
> > Please no attachments, as it makes it much harder to read the patch,
> > and comment on it:  
> 
> Thanks for having considered the patch.
> 
> >
> > https://elixir.bootlin.com/linux/v7.0/source/Documentation/process/submitting-patches.rst#L278
> >  
> 
> Is this a link? ;-)
> 
> --> No MIME, no links, no compression, no attachments. Just plain text  
> 
> You guys need a plugin for TUI e-mail readers/git-am that solves the
> text/base64 attachments issue.

Eh?
Not the least of the problems is that you (typically) have to explicitly
open the attachment in order to actually read it.
If it is inline you can just scroll down and give it a quick scan.

Have you ever tried reading patch attachments with what might be the
most common MUA on everything except phones?
You actually have to save them somewhere before you can open them.

	David

> 
> Seriously, someone should write it and write it in a manner that
> kernel guys are happy to adopt/use it.
> 
> It will be a great relief for both the sides (senders, receivers)
> because space/tab mismatch hurts as well.
> 
> While git-send requires some hard-to-grant precautions to not become a
> serious trouble / headache.
> 
> Best regards, R-
>