From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <kyle@kyleam.com>
Received: from mp2.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by ms1.migadu.com with LMTPS
	id mP1GIx2UyWV2SgAAe85BDQ:P1
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Mon, 12 Feb 2024 04:44:29 +0100
Received: from mta1.migadu.com ([2001:41d0:203:375::])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits))
	by mp2.migadu.com with LMTPS
	id mP1GIx2UyWV2SgAAe85BDQ
	(envelope-from <kyle@kyleam.com>)
	for <larch@inbox.kyleam.com>; Mon, 12 Feb 2024 04:44:29 +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=1707709469;
	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=uTxxHRXjH0MO3mghBzfy3bywuJovecX+jwMScuXz0uE=;
	b=d6UjZdan5csoiUQF6qR9J7lvqvyaAXv/3dOh3HtT7moL2gpO4QkmBk28wRjuB2MPkJEJdD
	GBAEy2ied1Brm7cWwhGyWQDUqZwNS8FVNDw0/5m/KcutMz1lT9ihQlCl0IlIUxDUoK2lRH
	tg7P0n2DdHYsMCN112ssrFzm5Gs3ILa7XG0HaFg40wHrY6fxOBLF3xxHO6Pq2XXIHf9+ch
	NjcDxHq2upfbFV/+Y8Frvo+spVaMCV8oJz3y31RgL0wSx9pkiYMob/hYA6Wnj1wMnwYFBG
	oZxcskqoUrQwfUrRV0VjyIEYA8fTVKHKnPT62nmWZyiZEMdw9mtPSQJRxfTgHA==
From: Kyle Meyer <kyle@kyleam.com>
To: Leo <git@relevant-information.com>
Cc: piem@inbox.kyleam.com
Subject: Re: [PATCH] *-am-ready-mbox: Don't require PATCH prefix
In-Reply-To: <87eddqnsja.fsf@kyleam.com>
References: <87ttmo57js.fsf@kyleam.com> <87eddqnsja.fsf@kyleam.com>
Date: Sun, 11 Feb 2024 22:44:25 -0500
Message-ID: <87eddiqrc6.fsf@kyleam.com>
MIME-Version: 1.0
Content-Type: text/plain
X-Migadu-Flow: FLOW_OUT
X-TUID: eLRwDDjXfOJg

Kyle Meyer writes:

> Leo writes:
>
>> The only comment I have is that running piem-am with this patch on a
>> non-patch buffer (and selecting a repo to apply it on) will create a new
>> branch and put git in a state of failing to apply a patch.  You need to
>> clean it up by deleting the branch and running `git am --abort` in the
>> repository.  This seems reasonable to me.  Both are easy to do, and is
>> what you would expect to happen if you run `git-am` with a broken patch
>> (well not really the branch, but I think that's fine).
>
> Right, that is worth spelling out.  Thanks.

Pushed (8abe70c) with a revised commit message.