[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d5b360c6-1ef4-4344-9ad5-91ba5d962183@p183>
Date: Tue, 13 May 2025 21:32:37 +0300
From: Alexey Dobriyan <adobriyan@...il.com>
To: Greg KH <gregkh@...uxfoundation.org>
Cc: Jonathan Corbet <corbet@....net>, workflows@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/9] CodingStyle: make Documentation/CodingStyle into
symlink
On Mon, May 12, 2025 at 06:57:49PM +0200, Greg KH wrote:
> On Mon, May 12, 2025 at 07:08:53PM +0300, Alexey Dobriyan wrote:
> > On Sat, May 10, 2025 at 04:05:29AM -0600, Jonathan Corbet wrote:
> > > Alexey Dobriyan <adobriyan@...il.com> writes:
> > >
> > > > Every time I open Documentation/CodingStyle it says the party moved
> > > > somewhere else. :-(
> > > >
> > > > Of course, I forget where it moved to by the next time.
> > > >
> > > > Signed-off-by: Alexey Dobriyan <adobriyan@...il.com>
> > > > ---
> > >
> > > No 0/9 cover letter?
> >
> > Not really. Cover letter would be very short:
> >
> > Tweak coding style to add things I've learned over the years of
> > Linux/C programming.
> >
> > And stop making kernel devs look like aliens from another Universe
> > (see static_assert() rule and especially(!) "declare ALAP" rule)
>
> Both of those are not valid reasons to change coding style, sorry.
Please read individual items.
I never liked cover letters because they don't get captured in
the commit messages so why bother.
> Again, learn about _why_ we have one,
> don't get bogged down in the details of _what_ it is.
CodingStyle is quite detailed at the moment.
Especially if some new details decreate bug rate a little.
Powered by blists - more mailing lists