From: Matthew Lien <bluet@bluet.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: bug-guix@gnu.org
Subject: Re: Tracking bugs
Date: Wed, 3 Jul 2013 15:49:10 +0800 [thread overview]
Message-ID: <CAGurB_iOQtp2DCJabqk6Jh=VBwppxUqDME3FYzM_kZr1+zEO0Q@mail.gmail.com> (raw)
In-Reply-To: <87ppv0d5bt.fsf@gnu.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=GB2312, Size: 1047 bytes --]
It'd nice to have bug tracking system, github or whatever. :-)
2013/7/3 Ludovic Court¨¨s <ludo@gnu.org>
> Hello!
>
> In line with our tireless efforts to achieve so-called ¡°industrial
> strength¡± for Guix, time has come to have a bug tracker.
>
> I¡¯m very much in favor of using <http://debbugs.gnu.org/>. Debbugs can
> be accessed by email, through its web interface, and via its Emacs
> interface. It¡¯s simple and nice. It¡¯s used by several GNU projects:
> <http://debbugs.gnu.org/Packages.html>.
>
> So, unless someone complains vehemently, I would like to have it ready
> by the next release (within 2 weeks?). That means we¡¯d create another
> list (guix-devel, say) for discussions, and bug-guix would be under
> Debbugs¡¯ control¨Cmeaning that any messages sent to bug-guix will lead to
> the creation of a new bug report.
>
> Thoughts?
>
> Thanks,
> Ludo¡¯.
>
>
--
/ Just another [ Perl | FOSS | Security ] Hacker. /
/ BlueT = Matthew Lien = ¾´Ã÷ /
/ http://BlueT.org /
/ GPG: 4A293CBD /
[-- Attachment #2: Type: text/html, Size: 1934 bytes --]
next prev parent reply other threads:[~2013-07-03 7:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-02 21:23 Tracking bugs Ludovic Courtès
2013-07-03 7:49 ` Matthew Lien [this message]
2013-07-06 23:14 ` Discussions moving to guix-devel@gnu.org! Ludovic Courtès
2013-07-07 9:45 ` Ludovic Courtès
2013-07-07 9:45 ` Ludovic Courtès
2013-07-10 21:43 ` Ludovic Courtès
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='CAGurB_iOQtp2DCJabqk6Jh=VBwppxUqDME3FYzM_kZr1+zEO0Q@mail.gmail.com' \
--to=bluet@bluet.org \
--cc=bug-guix@gnu.org \
--cc=ludo@gnu.org \
/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.