From: zimoun <zimon.toutoune@gmail.com>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Publishing news about Guix on a weekly basis
Date: Tue, 5 Nov 2019 17:13:14 +0100 [thread overview]
Message-ID: <CAJ3okZ3sLkqsbHq7dEMLt--eSdqpq2TFimRCVXXJ0reUm_adyQ@mail.gmail.com> (raw)
In-Reply-To: <20191105114849.3kqgeksu2lfiayhi@thebird.nl>
Hi,
To complement, some monthly information about debbugs should be nice
too; maybe provided by Mumi.
Some time ago [1] Pjotr proposed something like:
--8<---------------cut here---------------start------------->8---
Summary
Status
31 Outstanding
18 Resolved
Severity
49 Normal bugs
Classification
22 Patch Available
9 Unclassified
Patches older than 1 week:
gnu: mumble: Build with 'murmur' server component. Modified 13 days ago;
gnu: Add blists. Modified 13 days ago;
gnu: Add lush2. Modified 13 days ago;
etc.
--8<---------------cut here---------------end--------------->8---
And maybe
- 5 pointers to easy bugs
- 5 pointer to long standing bugs
etc.
All the best,
simon
[1] https://lists.gnu.org/archive/html/guix-devel/2017-02/msg01139.html
next prev parent reply other threads:[~2019-11-05 16:13 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-03 12:19 Publishing news about Guix on a weekly basis Christopher Baines
2019-11-04 6:41 ` L p R n d n
2019-11-05 8:17 ` Christopher Baines
2019-11-04 12:44 ` Pjotr Prins
2019-11-04 13:04 ` Pierre Neidhardt
2019-11-05 8:37 ` Christopher Baines
2019-11-09 17:26 ` Ludovic Courtès
2019-11-05 8:36 ` Christopher Baines
2019-11-05 11:48 ` Pjotr Prins
2019-11-05 16:13 ` zimoun [this message]
2019-11-07 19:34 ` Christopher Baines
2019-11-07 18:28 ` Christopher Baines
2019-11-06 16:17 ` Ludovic Courtès
2019-11-07 19:41 ` Christopher Baines
2019-11-09 17:26 ` Ludovic Courtès
2019-11-06 17:53 ` sirgazil
2019-11-07 19:52 ` Christopher Baines
2019-11-07 22:04 ` sirgazil
2019-11-09 17:33 ` Ludovic Courtès
2019-11-11 16:09 ` sirgazil
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=CAJ3okZ3sLkqsbHq7dEMLt--eSdqpq2TFimRCVXXJ0reUm_adyQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=pjotr.public12@thebird.nl \
/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.