Kernel keyring development
 help / color / mirror / Atom feed
From: Jarkko Sakkinen <jarkko@kernel.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: David Howells <dhowells@redhat.com>,
	Herbert Xu <herbert@gondor.apana.org.au>,
	"David S. Miller" <davem@davemloft.net>,
	keyrings@vger.kernel.org, linux-integrity@vger.kernel.org,
	Fabrice Derepas <fabrice.derepas@canonical.com>,
	Michael Bommarito <michael.bommarito@gmail.com>
Subject: Re: [GIT PULL] KEYS: for-next-keys-7.2-rc6
Date: Tue, 28 Jul 2026 03:50:50 +0300	[thread overview]
Message-ID: <amf86pBd_7wmh2Pf@kernel.org> (raw)
In-Reply-To: <amf8lG0-TnummN5Q@kernel.org>

On Tue, Jul 28, 2026 at 03:49:28AM +0300, Jarkko Sakkinen wrote:
> On Mon, Jul 27, 2026 at 02:22:47PM -0700, Linus Torvalds wrote:
> > On Mon, 27 Jul 2026 at 11:46, Jarkko Sakkinen <jarkko@kernel.org> wrote:
> > >
> > > This pull request contains bug fixes discussed in [1] and two fixes
> > > (in one commit) from Fabrice for DCP trusted keys backend..
> > 
> > Please don't explain commits with links. The commit log is supposed to
> > be legible without a network connection. Links are ok as supplements
> > and background information, but not as a "this is explained by link".
> > 
> > And the pull request is supposed to have what I can useas that commit
> > log (either in the email or in the tag). Yes, I edit things for
> > clarity and consistency, but I don't want to follow links and try to
> > figure out what some discussion was all about.
> > 
> > So please give me an explanation for what you are asking me to pull.
> > Both so that I see what I'm pulling, and so that I'll have a merge
> > message explaining things for later.
> > 
> > I've done this myself this time, but please make your pull requests
> > legible in the future. The patch series you merged even had a cover
> > letter, please keep track of these things and don't make people search
> > for them.
> > 
> >              Linus
> 
> I'll keep this is mind and yeah, get the frustration with this.

Right, and thanks for still merging it.

BR, Jarkko

  reply	other threads:[~2026-07-28  0:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-27 18:45 [GIT PULL] KEYS: for-next-keys-7.2-rc6 Jarkko Sakkinen
2026-07-27 21:22 ` Linus Torvalds
2026-07-28  0:49   ` Jarkko Sakkinen
2026-07-28  0:50     ` Jarkko Sakkinen [this message]
2026-07-27 21:50 ` pr-tracker-bot

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=amf86pBd_7wmh2Pf@kernel.org \
    --to=jarkko@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=fabrice.derepas@canonical.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=keyrings@vger.kernel.org \
    --cc=linux-integrity@vger.kernel.org \
    --cc=michael.bommarito@gmail.com \
    --cc=torvalds@linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox