From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp0.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms1.migadu.com with LMTPS id 4AYFI/0QvmUATwEAqHPOHw:P1 (envelope-from ) for ; Sat, 03 Feb 2024 11:10:05 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp0.migadu.com with LMTPS id 4AYFI/0QvmUATwEAqHPOHw (envelope-from ) for ; Sat, 03 Feb 2024 11:10:05 +0100 X-Envelope-To: piem@inbox.kyleam.com Authentication-Results: aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of git@relevant-information.com designates 80.241.56.152 as permitted sender) smtp.mailfrom=git@relevant-information.com ARC-Seal: i=1; s=key1; d=kyleam.com; t=1706955005; a=rsa-sha256; cv=none; b=S31jOAJwNHtYPBpVn1gY+CtQtCo3HMGYNLPeVF6ogFgnBjep09yvD5R3fMA+5e/Y14Wteu BajvcThdNbo7eaQlPjT+bZGO7HqaJ6eJihLEOwNfK2X2h4AnPl46SVqCs9QYfftdnpbKvX WosFEpx92KjsaTzoXXNrjo3wu7MJHB/Jgy3i88JRyLfGnYpgV6RMCveMeOrVqsLvKiMHuF 24anc3Bjgxiz15BYPyJ5ptPH7/utUvdomIXmhtODD/MhFINpyx44WUsh137WINTRWnHTMm yi/pI4rHEUgkB3yG987sDn5U/KPde5KssLGc1e0cUIUsvrWk+1IgLNwJ7E4TLA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=none; dmarc=none; spf=pass (aspmx1.migadu.com: domain of git@relevant-information.com designates 80.241.56.152 as permitted sender) smtp.mailfrom=git@relevant-information.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1; t=1706955005; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type; bh=ZcSfSCKOWP39qKY0Av8jL6JUug1Vo5t79PqQx0paA9k=; b=iQwHqWlPUp+r4i4Ulp0TvntwhT4B/r7q1hlaZgyJpJKJAByJB6mjnBiY0j41H0eMS66Jz3 OBfy/kg4CKvdJ7saWVhuK/nv2OI6F4HaaMO3rRUNpOdt74xeZt+OBnW8qzsjqitPgJoluZ BuIhKIqjytKvGn3sU7NTVSp43u8tG4rC17A+LtGXk3Y2dfUQwRZ5vCP+54b7DvIIZTedpW GaTInkCfcZ3lPGsbxA4cHR54cyYOttAfTCSLBXY6tXyxAmnbrsl6FMFHOWO4uPHBUoC/Qd M3BJY9kHHHufqDhtOZE9E+iy+wiaQH+vCx5xqKEK96BpDpTWkQ4xyy0nh5OsGQ== Received: from mout-p-102.mailbox.org (mout-p-102.mailbox.org [80.241.56.152]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id 026416BADE for ; Sat, 3 Feb 2024 11:10:01 +0100 (CET) Received: from smtp2.mailbox.org (smtp2.mailbox.org [10.196.197.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mout-p-102.mailbox.org (Postfix) with ESMTPS id 4TRpKX6MRHz9sTd for ; Sat, 3 Feb 2024 11:09:52 +0100 (CET) From: Leo To: piem@inbox.kyleam.com Subject: Could not find am-ready mbox for current buffer Date: Sat, 03 Feb 2024 11:09:49 +0100 Message-ID: <87fry9hn9u.fsf@> MIME-Version: 1.0 Content-Type: text/plain X-Migadu-Flow: FLOW_IN X-Migadu-Country: DE X-Migadu-Scanner: mx10.migadu.com X-Spam-Score: -2.80 X-Migadu-Queue-Id: 026416BADE X-Migadu-Spam-Score: -2.80 X-TUID: SfOgfKISPXKR Hello, This is really just for future reference, in case someone else stumbles upon this. I've resolved it for myself and am just documenting what the issue was. I found that for a specific email with a patch piem would just refuse to apply it with the message "Could not find am-ready mbox for current buffer", even if just piping the email through `git am` would work. Turns out the issue was with piem-patch-subject-re. The patch was sent with a different subject prefix (the --subject-prefix option in git-send-email) than the default, which didn't match piem-patch-subject-re. For example: > Subject: [RFC] add some code So if you, like me, just can't figure out why piem is angry with just this specific patch, consider adjusting that variable. Cheers, Leo