unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 65883@debbugs.gnu.org, ludo@gnu.org
Subject: [bug#65883] [PATCH] .dir-locals.el: Update bug-reference configuration and document it.
Date: Mon, 25 Sep 2023 13:27:03 -0400	[thread overview]
Message-ID: <87cyy62mfs.fsf@gmail.com> (raw)
In-Reply-To: <CAJ3okZ0Uhm4M=3JnNK_e22LOEp+6iMRk_ar=OxaTMPvA98LfEQ@mail.gmail.com> (Simon Tournier's message of "Mon, 25 Sep 2023 18:24:20 +0200")

Hi Simon,

Simon Tournier <zimon.toutoune@gmail.com> writes:

> Hi,
>
> On Mon, 25 Sept 2023 at 18:13, Maxim Cournoyer
> <maxim.cournoyer@gmail.com> wrote:
>
>> >> Thanks for pointing these other possibilities.  Unless they are
>> >> prominently documented though, I'd maybe opt to leave them out, as their
>> >> format simply uses more characters for no added value.
>> >
>> > What I have noticed is the way Mumi resolves from Message-ID to Debbugs-ID:
>> >
>> > https://issues.guix.gnu.org/msgid/63a33d011b9154bbb4de7ad1d183043220fec49a.1691432343.git.h.goebel@crazy-compilers.com
>> >     ->
>> > https://issues.guix.gnu.org/issue/65131#msgid-4f7b841a5c1ab6ea0ee22d3bbd2bedab2ed435fa
>> >
>> > And this case could be handled, no?
>>
>> I'm not sure how it'd work; bug-reference understand a simple full bug
>> URLs, not ones pointing to a particular message.
>
> I was answering about "Unless they are prominently documented though"
> by mentioning the /issue/ part is there when Mumi resolves from
> Message-ID to Debbugs-ID.  Well, "prominently" documented when
> speaking about Mumi is difficult to evaluate. ;-)  Instead, I notice
> Mumi uses it.
>
> And I was asking about the regular expression for
> https://issues.guix.gnu.org/issue/65131#msgid-4f7b841a5c1ab6ea0ee22d3bbd2bedab2ed435fa
> where bug-reference can extract 65131.
>
> Somehow, I think that the regular expression of bug-reference should
> handle https://issues.guix.gnu.org/issue/12345 in addition to
> https://issues.guix.gnu.org/12345.  And bonus for
> https://issues.guix.gnu.org/issue/65131#msgid-[:alnum:] :-)

OK, thanks for explaining.  I don't object to the proposed change, but
I'll pass on the implementation :-).

-- 
Thanks,
Maxim




      reply	other threads:[~2023-09-25 17:27 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-12  3:44 [bug#65883] [PATCH] .dir-locals.el: Update bug-reference configuration and document it Maxim Cournoyer
2023-09-12 14:20 ` brian via Guix-patches via
2023-09-12 14:34 ` brian via Guix-patches via
2023-09-17 20:45   ` bug#65883: " Maxim Cournoyer
2023-09-13 20:31 ` [bug#65883] " Ludovic Courtès
2023-09-14  3:20   ` Maxim Cournoyer
2023-09-19  8:08 ` Simon Tournier
2023-09-20 15:28   ` Maxim Cournoyer
2023-09-20 15:39     ` Simon Tournier
2023-09-25 16:13       ` Maxim Cournoyer
2023-09-25 16:24         ` Simon Tournier
2023-09-25 17:27           ` Maxim Cournoyer [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87cyy62mfs.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=65883@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).