From: Andreas Enge <andreas@enge.fr>
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel@gnu.org, ng0 <ng0@n0.is>
Subject: Re: Tracking package submissions with Debbugs
Date: Sun, 4 Sep 2016 09:05:09 +0200 [thread overview]
Message-ID: <20160904070509.GA1724@solar> (raw)
In-Reply-To: <87bn041jch.fsf@gmail.com>
Hello,
using debbugs corresponds to a suggestion I made a while ago, so I am
obviously in favour of it...
On Sun, Sep 04, 2016 at 10:37:02AM +0800, Alex Vong wrote:
> > I think it would make sense to have the one bug report for the "target
> > package" and then all the packages that get pulled in along the way get
> > tacked on also.
> Hmm, but what if we have 2 target packages (A, B) pulling the same
> package (C) in? Then it is not obvious if C should live in A's or B's
> bug report. What do you think?
I do not quite understand the problem with relating bug reports to packages.
The discussion sounds as if we considered one constantly open bug report per
package, which is maybe a misunderstanding on my part. I would say that bug
reports should correspond roughly to our current discussion threads on
guix-devel: Someone sends in a patch or patch series, which opens a new bug
(there seems to be the problem of git-sendmail still); there are replies back
and forth; in the end the patch is applied (or, from time to time, retracted),
and the bug is closed. In this way, we have an overview of pending patches
and are less likely to forget one.
As for the non-emacs users, I intend to work as before: Subscribe to all the
bugs and have them end up in my mailbox, reply, and potentially close them
by mail.
Andreas
next prev parent reply other threads:[~2016-09-04 7:05 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160904070509.GA1724@solar \
--to=andreas@enge.fr \
--cc=alexvong1995@gmail.com \
--cc=guix-devel@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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.