unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Arun Isaac <arunisaac@systemreboot.net>
To: zimoun <zimon.toutoune@gmail.com>,
	Leo Famulari <leo@famulari.name>,
	Maxime Devos <maximedevos@telenet.be>,
	Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Debbugs usertags with Mumi or Emacs (was: Assisting reviewing & committing with tags?)
Date: Tue, 03 May 2022 23:09:51 +0530	[thread overview]
Message-ID: <87y1zicy6w.fsf@systemreboot.net> (raw)
In-Reply-To: <868rrij2ts.fsf@gmail.com>


Hi zimoun,

>> This is a great idea. I guess we will need to adjust the software that
>> runs issues.guix.gnu.org to make use of it, but in the meantime you
>> should keep using this tag. Thanks!
>
> Indeed, Mumi does not expose such user tags.  Well, it could be very
> useful if such tags would be available via GraphQL requests.
>
> Arun, Ricardo, do you think it is affordable?

I haven't explored debbugs' usertags closely yet, and I'm not sure how
exactly it works. But, usertags are certainly the way to go
forward.

Maybe, a quick way to start would be to start setting usertags through
the existing debbugs email interface, and getting mumi to display them
at https://issues.guix.gnu.org

Cheers,
Arun


      parent reply	other threads:[~2022-05-03 17:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-09 10:54 Assisting reviewing & committing with tags? Maxime Devos
2022-01-11 19:10 ` Leo Famulari
2022-02-02 13:58   ` Maxim Cournoyer
2022-02-15 12:23     ` Bengt Richter
2022-02-15 16:23       ` Maxime Devos
2022-03-21  8:47         ` Bengt Richter
2022-05-03 11:03   ` Debbugs usertags with Mumi or Emacs (was: Assisting reviewing & committing with tags?) zimoun
2022-05-03 16:10     ` Maxime Devos
2022-05-03 17:39     ` Arun Isaac [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=87y1zicy6w.fsf@systemreboot.net \
    --to=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=leo@famulari.name \
    --cc=maximedevos@telenet.be \
    --cc=rekado@elephly.net \
    --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).