All of lore.kernel.org
 help / color / mirror / Atom feed
From: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: Linus Torvalds <torvalds@linuxfoundation.org>,
	Geert Uytterhoeven <geert@linux-m68k.org>,
	tools@linux.kernel.org, users@linux.kernel.org
Subject: Re: b4-0.9.0 available
Date: Tue, 21 Jun 2022 14:29:53 -0400	[thread overview]
Message-ID: <20220621182953.p5asczznnz3pn6dl@meerkat.local> (raw)
In-Reply-To: <YrIEnmt5vDMcbOiG@zx2c4.com>

On Tue, Jun 21, 2022 at 07:49:18PM +0200, Jason A. Donenfeld wrote:
> IMO, you should remove both the "sort S-o-b into meaninglessness" and
> the "add a useless Link: trailer that wastes my time when I middle click
> it" options, so that it's harder to make these mistakes.

I mean, I'm happy to make any changes, but I implemented these in the first
place as a response to requests or established practices. Some maintainers do
very much like to sort their trailers, and others like to link to the list
origins of the patch.

If there is someone who is willing to compile a definitive list of "Linux
Kernel commit do's and dont's", then I'll happily stick to that.

For now, the default operation is already exactly as you ask -- we neither
sort the trailers nor add the link unless both of these are explicitly
requested.

-K

  reply	other threads:[~2022-06-21 18:29 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 19:01 b4-0.9.0 available Konstantin Ryabitsev
2022-06-20  8:40 ` Geert Uytterhoeven
2022-06-21 23:38   ` Linus Walleij
2022-06-22  5:49     ` Vinod Koul
2022-06-21 15:20 ` Geert Uytterhoeven
2022-06-21 15:29   ` Konstantin Ryabitsev
2022-06-21 15:41     ` Geert Uytterhoeven
2022-06-21 15:55       ` Linus Torvalds
2022-06-21 16:03         ` Jason A. Donenfeld
2022-06-21 16:59           ` Konstantin Ryabitsev
2022-06-21 17:49             ` Jason A. Donenfeld
2022-06-21 18:29               ` Konstantin Ryabitsev [this message]
2022-06-21 18:45                 ` Jason A. Donenfeld
2022-06-21 19:27                   ` Konstantin Ryabitsev
2022-06-21 19:42                     ` Jason A. Donenfeld
2022-06-21 19:43                     ` Geert Uytterhoeven
2022-06-21 19:50                       ` Jason A. Donenfeld
2022-06-21 20:06                         ` Konstantin Ryabitsev
2022-06-21 20:29                           ` Jason A. Donenfeld
2022-06-21 21:25                   ` Bjorn Andersson
2022-06-23 23:33                     ` Theodore Ts'o
2022-06-24 13:51                       ` Jason Gunthorpe
2022-06-24 15:29                         ` Theodore Ts'o
2022-06-24 15:34                           ` Mark Brown
2022-06-24 16:05                             ` Theodore Ts'o
2022-06-24 15:52                           ` Konstantin Ryabitsev
2022-06-24 16:05                             ` James Bottomley
2022-06-24 16:16                               ` Konstantin Ryabitsev
2022-06-24 16:29                                 ` James Bottomley
2022-06-24 16:06                             ` Jason Gunthorpe
2022-06-24 16:16                               ` Mark Brown
2022-06-24 17:51                           ` Chuck Lever
2022-06-24  8:34                     ` Nicolas Ferre
2022-06-21 15:53     ` Jason A. Donenfeld

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20220621182953.p5asczznnz3pn6dl@meerkat.local \
    --to=konstantin@linuxfoundation.org \
    --cc=Jason@zx2c4.com \
    --cc=geert@linux-m68k.org \
    --cc=tools@linux.kernel.org \
    --cc=torvalds@linuxfoundation.org \
    --cc=users@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.