From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org, ng0 <ng0@n0.is>
Subject: Re: Tracking package submissions with Debbugs
Date: Fri, 2 Sep 2016 16:29:13 +0200 [thread overview]
Message-ID: <idjr392gyti.fsf@bimsb-sys02.mdc-berlin.net> (raw)
In-Reply-To: <87fupimq6n.fsf_-_@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> I suppose it wouldn’t handle patch series very well though, would it?
> Or people would have to send the “cover letter” of the series first, and
> then send the rest to NNN@debbugs.gnu.org once a number has been
> assigned?
Or could we have a bug per module? Then the whole patch series could be
sent to the bug id of the module. But I guess this would make it harder
to keep track of individual package submissions again, because bug would
rarely ever be closed when there are lots of patches to the same module.
> What’s unclear to me is how convenient Debbugs is for non-Emacs users:
> Emacs has M-x debbugs-gnu, which is a significant UI improvement, but
> how do non-Emacs users deal with Debbugs?
Outside of Emacs I only ever used Debbugs in read-only fashion. The web
interface is not very pretty but it’s functional and looks better than
the default mailman interface.
~~ Ricardo
next prev parent reply other threads:[~2016-09-02 14:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-13 10:46 Feedback, ideas, discussion: tracking patches, discussions, bugs David Craven
2016-08-13 11:11 ` David Craven
2016-08-13 11:23 ` ng0
2016-08-14 5:41 ` Pjotr Prins
2016-08-14 9:14 ` ng0
2016-08-15 1:39 ` David Craven
2016-08-15 4:55 ` Pjotr Prins
2016-08-15 9:11 ` David Craven
2016-08-16 13:17 ` Ricardo Wurmus
2016-08-16 13:29 ` Pjotr Prins
2016-08-15 11:53 ` Hartmut Goebel
2016-08-15 13:30 ` Danny Milosavljevic
2016-08-15 15:18 ` Alex Vong
2016-08-16 7:20 ` Hartmut Goebel
2016-08-16 14:06 ` Alex Vong
2016-08-18 11:47 ` Hartmut Goebel
2016-09-01 6:32 ` ng0
2016-09-01 11:19 ` ng0
2016-09-02 0:27 ` John Darrington
2016-09-02 0:58 ` ng0
2016-09-02 5:50 ` Alex Vong
2016-09-02 8:21 ` ng0
2016-09-02 10:54 ` Alex Vong
2016-09-03 16:44 ` Pjotr Prins
2016-09-03 16:55 ` David Craven
2016-09-03 19:19 ` Brendan Tildesley
2016-09-03 19:53 ` David Craven
2016-09-03 20:42 ` Efraim Flashner
2016-09-02 12:39 ` Tracking package submissions with Debbugs Ludovic Courtès
2016-09-02 14:29 ` Ricardo Wurmus [this message]
2016-09-03 0:35 ` Alex Vong
2016-09-03 13:47 ` Ludovic Courtès
2016-09-04 2:21 ` Alex Vong
2016-09-03 21:00 ` Efraim Flashner
2016-09-04 2:37 ` Alex Vong
2016-09-04 7:05 ` Andreas Enge
2016-09-04 16:57 ` ng0
2016-09-04 17:00 ` ng0
2016-09-04 17:09 ` David Craven
2016-09-05 12:52 ` Alex Kost
2016-09-05 20:22 ` Ludovic Courtès
2016-09-05 20:39 ` David Craven
2016-09-05 23:12 ` ng0
2016-09-07 20:38 ` Ludovic Courtès
2016-09-05 23:17 ` ng0
2016-09-05 23:54 ` David Craven
2016-09-06 0:01 ` Ben Woodcroft
2016-09-06 7:57 ` ng0
2016-09-06 11:26 ` David Craven
2016-09-06 1:24 ` Alex Vong
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=idjr392gyti.fsf@bimsb-sys02.mdc-berlin.net \
--to=ricardo.wurmus@mdc-berlin.de \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=ng0@n0.is \
/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).