From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Mumi now uses raw emails and Mu
Date: Wed, 24 Jul 2019 19:45:20 +0200
Message-ID: <87blxjba33.fsf@elephly.net>
References: <87ef2jdtuc.fsf@elephly.net>
 <alpine.DEB.2.20.1907212035220.9756@marsh.hcoop.net>
 <87blxme6pk.fsf@elephly.net> <875zntc8ux.fsf@elephly.net>
 <cu7y30ne4z7.fsf@systemreboot.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:470:142:3::10]:59533)
 by lists.gnu.org with esmtp (Exim 4.86_2)
 (envelope-from <rekado@elephly.net>) id 1hqLKf-0003Oj-L5
 for guix-devel@gnu.org; Wed, 24 Jul 2019 13:45:42 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
 (envelope-from <rekado@elephly.net>) id 1hqLKe-0000eW-FY
 for guix-devel@gnu.org; Wed, 24 Jul 2019 13:45:41 -0400
Received: from sender4-of-o53.zoho.com ([136.143.188.53]:21348)
 by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32)
 (Exim 4.71) (envelope-from <rekado@elephly.net>) id 1hqLKd-0000bE-Vm
 for guix-devel@gnu.org; Wed, 24 Jul 2019 13:45:40 -0400
In-reply-to: <cu7y30ne4z7.fsf@systemreboot.net>
List-Id: "Development of GNU Guix and the GNU System distribution."
 <guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <https://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
 <mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: guix-devel@gnu.org


Arun Isaac <arunisaac@systemreboot.net> writes:

>> I forked Mu and let it store the =E2=80=9CX-Debbugs-Envelope-To=E2=80=9D=
 header in the
>> database:
>>
>>     https://git.elephly.net/?p=3Dsoftware/mumimu.git;a=3Dshortlog;h=3Dre=
fs/heads/mumimu
>>
>> This seems to actually work.  Still don=E2=80=99t know if all emails act=
ually
>> have that header; if they don=E2=80=99t we=E2=80=99ll need to implement =
an alternative
>> way to get the bug number in =E2=80=9Cget_bugid=E2=80=9D (lib/mu-msg-fil=
e.c).
>
> Can't we find the bug number of an email by matching the To and Cc
> addresses against xxxxx@debbugs.gnu.org where xxxxx is a bug number?

No because the initial email would be sent to bug-guix@gnu.org or
guix-patches@gnu.org, not xxxxx@debbugs.gnu.org.

There are also some control messages which are not sent to
xxxxx@debbugs.gnu.org but are received by the Debbugs service through
other means.

I=E2=80=99m now getting the bug number by convention: mumi gets them from
Debbugs, stores them in a predictable fashion (<bugnum> dash <msgnum>),
and mumimu gets the bug number from that file name.

Since mumimu isn=E2=80=99t a general purpose tool we can get away with that=
 if
we all just hold our noses and ignore the stench.

--
Ricardo