public inbox for cip-dev@lists.cip-project.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@denx.de>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: Paul Barker <paul.barker.ct@bp.renesas.com>,
	Pavel Machek <pavel@denx.de>,
	Michael Adler <michael.adler@siemens.com>,
	cip-dev@lists.cip-project.org, Ulrich Hecht <uli@kernel.org>
Subject: Re: [cip-dev] Mailing list inventing addresses for people
Date: Mon, 17 Mar 2025 14:26:51 +0100	[thread overview]
Message-ID: <Z9gjG+wML3dUdjSK@duo.ucw.cz> (raw)
In-Reply-To: <7554ef00-6a86-41a4-837a-183681f9e1a0@siemens.com>

[-- Attachment #1: Type: text/plain, Size: 1247 bytes --]

Hi!

> Indeed. Happened to me in the past as well, but now I have local tooling
> in place that warns here when it checks from: against signed-off-by.
> 
> Jan
> 
> PS: Pavel, you wanted to forward a message to me where the sender is
> mangled and the "reply-to" is set to the list.

I can't get you full message. Mailing list is stupid enough to include
secrets (!) in it. Here are important headers:

From: "Quirin Gylstorff via lists.cip-project.org" <quirin.gylstorff=siemens.com@lists.cip-project.org>
To: jan.kiszka@siemens.com,
        felix.moessbauer@siemens.com,
        cip-dev@lists.cip-project.org,
        gokhan.cetin@siemens.com
Subject: [cip-dev][isar-cip-core][RFC] Add documentation to provide project specific signing methods
Message-ID: <20250317112102.609922-1-Quirin.Gylstorff@siemens.com>
Delivered-To: mailing list cip-dev@lists.cip-project.org
Resent-Date: Mon, 17 Mar 2025 04:21:08 -0700
Resent-From: quirin.gylstorff@siemens.com
Reply-To: cip-dev@lists.cip-project.org

I'll get you redacted copy in private email

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

      reply	other threads:[~2025-03-17 13:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-13 12:34 Mailing list inventing addresses for people Pavel Machek
2025-03-13 13:08 ` Jan Kiszka
2025-03-13 13:44   ` [cip-dev] " Michael Adler
2025-03-13 13:56     ` Pavel Machek
2025-03-17  9:35       ` Paul Barker
2025-03-17  9:57         ` Jan Kiszka
2025-03-17 13:26           ` Pavel Machek [this message]

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=Z9gjG+wML3dUdjSK@duo.ucw.cz \
    --to=pavel@denx.de \
    --cc=cip-dev@lists.cip-project.org \
    --cc=jan.kiszka@siemens.com \
    --cc=michael.adler@siemens.com \
    --cc=paul.barker.ct@bp.renesas.com \
    --cc=uli@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox