Received: from listserv.local (listserv [172.16.8.22])
	by nld3-dev1.alpinelinux.org (Postfix) with ESMTP id E8638780EDB;
	Wed, 12 Jan 2022 21:46:49 +0000 (UTC)
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
To: Thiago Perrotta <tbperrotta@gmail.com>
From: Thiago Perrotta <no-reply@dispatch.alpinelinux.org>
Cc: alpine-aports@lists.alpinelinux.org
In-Reply-To: 
 <164197467977.985.2207901805820716510.gitlab.28364.16580d4312e60df090422c6f24031e77a1eb9cfb@listserv.local>
Subject: Re: [PATCH] testing/fpp: new aport
Date: Wed, 12 Jan 2022 21:46:49 -0000
Message-ID: 
 <164202400991.985.5628697366313659577.gitlab.28364.16580d4312e60df090422c6f24031e77a1eb9cfb@listserv.local>

I did this before, but the caveat is that it ends up creating several MRs in Gitlab, which must be manually closed.

c.f. https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests?scope=all&state=closed&search=urlwatch and https://lists.alpinelinux.org/~alpine/aports?search=urlwatch (note: in this case I forgot to add -v2, -v3 etc but the point still applies).

The current optimal (least noisy) way seems to be to use the Gitlab workflow, with a MR owned by the contributor. Which is a bit sad because I am a fan of the email workflow.


Anyway, noted, I will stop using `--in-reply-to` for the time being, thanks Drew.

-- 
via https://gitlab.alpinelinux.org/alpine/aports/-/merge_requests/28364#note_205861