All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Linus Torvalds <torvalds@linuxfoundation.org>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	 Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
	tools@linux.kernel.org,  users@linux.kernel.org
Subject: Re: b4-0.9.0 available
Date: Tue, 21 Jun 2022 18:03:30 +0200	[thread overview]
Message-ID: <CAHmME9p+zRErOsvA1zC=kTHtpYD_sGjFxVsj0pMwteAp4dCdjQ@mail.gmail.com> (raw)
In-Reply-To: <CAHk-=wiQzp+aurcmj15=LAa2ntvRZH0Ee2dn-PLjcFpmRE6Jcw@mail.gmail.com>

On 6/21/22, Linus Torvalds <torvalds@linuxfoundation.org> wrote:
> On Tue, Jun 21, 2022 at 10:41 AM Geert Uytterhoeven
> <geert@linux-m68k.org> wrote:
>>
>> FWIW, I follow the chain-of-custody ordering.
>
> I don't think different kinds of links have any particular ordering,
> but yes,the "Signed-off-by:" ones should basically be sorted by
> "author -> email chain -> committer" order so that you can see which
> actual "path" the patch took.
>

Very much so. But if you look at various commits from the last 2 or 3
years, this is now disregarded pretty regularly. It'd be nice to see
the tooling preventing this kind of error rather than encouraging it.

Jason

  reply	other threads:[~2022-06-21 16:03 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 [this message]
2022-06-21 16:59           ` Konstantin Ryabitsev
2022-06-21 17:49             ` Jason A. Donenfeld
2022-06-21 18:29               ` Konstantin Ryabitsev
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='CAHmME9p+zRErOsvA1zC=kTHtpYD_sGjFxVsj0pMwteAp4dCdjQ@mail.gmail.com' \
    --to=jason@zx2c4.com \
    --cc=geert@linux-m68k.org \
    --cc=konstantin@linuxfoundation.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.