unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: "Maxime Devos" <maximedevos@telenet.be>,
	"Ludovic Courtès" <ludo@gnu.org>,
	"Tobias Kortkamp" <tobias.kortkamp@gmail.com>,
	guix-devel@gnu.org
Subject: Re: Missing tags in Debbugs?
Date: Wed, 29 Jun 2022 15:45:27 +0200	[thread overview]
Message-ID: <20220629134527.GA2422@LionPure> (raw)
In-Reply-To: <86mtdwc4hb.fsf@gmail.com>

On +2022-06-29 09:29:20 +0200, zimoun wrote:
> Hi,
> 
> Thanks for the feed back
> 
> On Wed, 29 Jun 2022 at 08:07, bokr@bokr.com wrote:
> 
> > Anyway, the idea is to make the Subject: line greppable for both
> > what the bug is about and its status when it was closed.
> 
> I agree that it is hard to work with the Debbugs archive.  What you are
> asking seems possible with Debbugs but the GNU instance is not
> supporting many tags [1].  Using the ’Subject:’ line as tagging system
> could be a workaround but I am not convinced the ratio effort /
> usefulness is worth because it is too error-prone, IMHO.
> 
> Arun has presented nice ideas about improving Mumi and it appears to me
> the direction to go.
> 
> 
> 1: <https://debbugs.gnu.org/Developer.html#tags>

Thanks, that LGTM: Looks like easy-to-parse html :)

This looks interesting too, that I just found:

2: <https://debbugs.gnu.org/server-request.html#introduction>

Will have to try it. Maybe emacs already has a mode for that?
(I need to refresh my emacs-fu ;/ )
> 
> 
> Cheers,
> simon
--
Regards,
Bengt Richter


  reply	other threads:[~2022-06-29 14:20 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <6d31ff958ec0c75cbba8324a275315d195a54902.1653045472.git.tobias.kortkamp@gmail.com>
     [not found] ` <87sfntu6ft.fsf@gnu.org>
     [not found]   ` <b6d482002f7773e65e02dbbbf354e1c0178b823a.camel@telenet.be>
2022-06-27 10:10     ` Dealing with upstream issues Ludovic Courtès
2022-06-27 10:30       ` Maxime Devos
2022-06-27 10:37         ` Maxime Devos
2022-06-27 12:32           ` zimoun
2022-06-27 14:20             ` Maxime Devos
2022-06-27 15:06               ` zimoun
2022-06-27 15:41                 ` Maxime Devos
2022-06-28 11:01         ` zimoun
2022-06-28 12:21           ` Maxime Devos
2022-06-28 16:21             ` zimoun
2022-06-28 16:47               ` Maxime Devos
2022-06-28 17:36                 ` zimoun
2022-06-28 20:03                   ` Maxime Devos
2022-06-28 12:22           ` Maxime Devos
2022-06-28 12:31           ` Maxime Devos
2022-06-28 16:25             ` zimoun
2022-06-28 16:47               ` Maxime Devos
2022-06-29  6:07               ` bokr
2022-06-29  7:29                 ` Missing tags in Debbugs? zimoun
2022-06-29 13:45                   ` Bengt Richter [this message]
2022-06-30 11:53         ` Dealing with upstream issues Ludovic Courtès
2022-06-27 12:53       ` zimoun
2022-06-27 14:32         ` Maxime Devos
2022-06-27 15:23           ` zimoun
2022-06-27 15:47             ` Maxime Devos
2022-06-27 16:03             ` Maxime Devos
2022-06-27 16:14             ` Maxime Devos

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=20220629134527.GA2422@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=maximedevos@telenet.be \
    --cc=tobias.kortkamp@gmail.com \
    --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).