patches and low-level development discussion
 help / color / mirror / code / Atom feed
From: Alyssa Ross <hi@alyssa.is>
To: devel@spectrum-os.org
Cc: Demi Marie Obenour <demiobenour@gmail.com>
Subject: [PATCH] Documentation: request patches not to be PGP signed
Date: Thu, 26 Jun 2025 10:45:36 +0200	[thread overview]
Message-ID: <20250626084536.28688-1-hi@alyssa.is> (raw)

Just ran into this.  In future we could potentially consider
encouraging attestation using patatt[1] instead.

This documentation page is a bit buried, but I don't think there's
currently a better place.  I'm hoping that at some point we'll do a
full documentation reorganization.

Link: https://people.kernel.org/monsieuricon/end-to-end-patch-attestation-with-patatt-and-b4 [1]
Signed-off-by: Alyssa Ross <hi@alyssa.is>
---
 Documentation/contributing/working-with-patches.adoc | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/Documentation/contributing/working-with-patches.adoc b/Documentation/contributing/working-with-patches.adoc
index dfd4ed5..8e22343 100644
--- a/Documentation/contributing/working-with-patches.adoc
+++ b/Documentation/contributing/working-with-patches.adoc
@@ -4,9 +4,13 @@
 :page-has_children: true
 
 // SPDX-FileCopyrightText: 2022 Unikie
+// SPDX-FileCopyrightText: 2025 Alyssa Ross <hi@alyssa.is>
 // SPDX-License-Identifier: GFDL-1.3-no-invariants-or-later OR CC-BY-SA-4.0
 
 Patches are the way for contributors to submit code to the Spectrum project.
 
+Please do not sign patch emails with OpenPGP, as `git am` currently
+can't handle it.
+
 Make sure to xref:b4.adoc[install and configure the b4 utility] for
 applying and testing other people's patches.

base-commit: 979bd3090215048fc6815abb2189b4d1809c98ef
-- 
2.49.0


             reply	other threads:[~2025-06-26  8:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-26  8:45 Alyssa Ross [this message]
2025-06-28 20:01 ` [PATCH] Documentation: request patches not to be PGP signed Alyssa Ross

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=20250626084536.28688-1-hi@alyssa.is \
    --to=hi@alyssa.is \
    --cc=demiobenour@gmail.com \
    --cc=devel@spectrum-os.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.
Code repositories for project(s) associated with this public inbox

	https://spectrum-os.org/git/crosvm
	https://spectrum-os.org/git/doc
	https://spectrum-os.org/git/mktuntap
	https://spectrum-os.org/git/nixpkgs
	https://spectrum-os.org/git/spectrum
	https://spectrum-os.org/git/ucspi-vsock
	https://spectrum-os.org/git/www

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).