From: ludo@gnu.org (Ludovic Courtès)
To: bug-guix@gnu.org
Cc: guix-devel@gnu.org
Subject: Discussions moving to guix-devel@gnu.org!
Date: Sun, 07 Jul 2013 01:14:24 +0200 [thread overview]
Message-ID: <87ehbbmgbz.fsf@gnu.org> (raw)
In-Reply-To: <87ppv0d5bt.fsf@gnu.org> ("Ludovic \=\?utf-8\?Q\?Court\=C3\=A8s\=22'\?\= \=\?utf-8\?Q\?s\?\= message of "Tue, 02 Jul 2013 23:23:18 +0200")
[-- Attachment #1: Type: text/plain, Size: 1057 bytes --]
ludo@gnu.org (Ludovic Courtès) skribis:
> 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–meaning that any messages sent to bug-guix will lead to
> the creation of a new bug report.
Following this plan, I’ve created the guix-devel@gnu.org mailing list
for discussions. Please subscribe from there:
https://lists.gnu.org/mailman/listinfo/guix-devel
I will ask for Debbugs to grab messages sent to bug-guix@gnu.org within
a couple of weeks, at which point bug-guix will be a bug-report-only list.
Sorry for the inconvenience, and see you on guix-devel! :-)
Ludo’.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next parent reply other threads:[~2013-07-06 23:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87ppv0d5bt.fsf@gnu.org>
2013-07-06 23:14 ` Ludovic Courtès [this message]
2013-07-07 9:45 ` Discussions moving to guix-devel@gnu.org! 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
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=87ehbbmgbz.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=bug-guix@gnu.org \
--cc=guix-devel@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 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).