From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
Received: from mp0.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms19.migadu.com with LMTPS
	id SNsLFweqJ2fuKgAAqHPOHw:P1
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Sun, 03 Nov 2024 17:51:19 +0100
Received: from mta1.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp0.migadu.com with LMTPS
	id SNsLFweqJ2fuKgAAqHPOHw
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Sun, 03 Nov 2024 17:51:19 +0100
X-Report-Abuse: Please report any abuse attempt to abuse@migadu.com and include these headers.
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kyleam.com; s=key1;
	t=1730652678;
	h=from:from:reply-to:subject:subject:date:date:message-id:message-id:
	 to:to:cc:cc:mime-version:mime-version:content-type:content-type:
	 in-reply-to:in-reply-to:references:references;
	bh=ujCGaM9ybUA8BjxCAKfplU6MwYGUZXWXqLZDw8Dx+H0=;
	b=cfKMYUR5ASlJMV9xF1cTR+3+qD+H62dTAyHo6QmGb4LD/FtyssGr4U7D+H1wuNlEUMS9wE
	GvAs4Xd5dvFk2a2SHh/IPmTFQDeRajRGCDe2CVAB8V5edXCZHWIOGpMMqmgmMPVi+a7SQS
	EGMvaVPtBBjR4gtzTY1TsYQ0wdPCWFAZczmunt7NAu3omBCErwyFs1kwFYdUhG2ITP+4rx
	Gty9XyJDQfCvNquLUwIvBqmXROmBPtjPs1FRJ3A9x7YRfoGR+KGnj3sncDml5MHxIZspbK
	kZf1NFl9Js7mfgMj5dsDwZFH2AwJZpVZ+mZ6aHeW70IlHTPy+Qo6BEytwGFFeg==
From: Kyle Meyer <kyle@kyleam.com>
To: Leo <git@relevant-information.com>
Cc: piem@inbox.kyleam.com
Subject: Re: piem-am with multiple attached patches squashes the commits
In-Reply-To: <8734rnlmpd.fsf@>
References: 
Date: Sun, 03 Nov 2024 11:51:14 -0500
Message-ID: <87r07s45x9.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-TUID: LppHUEMQfY5h

Thanks for the report, and sorry for the very delayed reply.

Leo writes:

> I'm writing this as I've observed this presumably unintended behaviour
> once.  If you need more info I can try to reproduce in a more controlled
> environment.
>
> I got an email with a patch series with two commits, as attachments to a
> single email.  Something like this in notmuch:
>
> [ 0001-first-patch.patch: text/x-patch (hidden) ]
> [ 0002-second-patch.patch: text/x-patch (hidden) ]
>
> I called piem-am  on this, which managed to apply the patches.
> However, this resulted in a single commit with the commit message of the
> first patch, but the changes of both patches combined.

Odd.  I'm not able to trigger that behavior on my end, so any additional
info for reproducing would be helpful (though, if you're not hitting
into this regularly, I realize these details may be lost to time at this
point).