From: Pjotr Prins <pjotr.public12@thebird.nl>
To: ng0 <contact.ng0@cryptolab.net>
Cc: guix-devel@gnu.org
Subject: Re: Structured list of my patches
Date: Thu, 2 Feb 2017 04:05:00 +0000 [thread overview]
Message-ID: <20170202040500.GA1967@mail.thebird.nl> (raw)
In-Reply-To: <8760ktzbdr.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me>
Thanks ng0,
Embarrassing.
At FOSDEM I'll bring up the topic again of our submission system. Good
topic for the 'Future of Guix' panel.
Pj.
On Thu, Feb 02, 2017 at 12:26:08AM +0000, ng0 wrote:
> Recently I started to sent 3 classes of patches, and hoped that
> the coverletters description would help. Apparently it doesn't.
>
> I will add the lists.gnu.org archive links as I don't think the
> majority of people here can search for mailids with their mail
> readers.
>
> I am pretty sure I missed some patches, but that's it for now.
> Looking at the public[0] part of my branches, I have about 15-20
> more batches of packages I must drop/finish/get rid off so that I
> can focus on my work again.
>
> * Patches which need QA review (considered DONE from my side)
>
> * no-more-secrets
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02365.html
> * sedsed
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02336.html
> * libextractor inputs
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02319.html
> * blists
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02316.html
> * tinycm
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02308.html
> * python-pykka (I won't debbug the testsuite and will drop this
> at the end of the month, but I am willing apply small
> changes)
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02272.html
> * mbedtls, hiawatha
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02105.html
> * Murmur (mumble server)
> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00021.html
> * emacs-pretty-mode
> https://lists.gnu.org/archive/html/guix-devel/2017-02/msg00017.html
> * lush2
> * scsh
> * shadow (update)
>
> * Patches which are dropped from my tree (ie: deleted), free for
> others to pick up
>
> * supercollider
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02284.html
> * Krita
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02294.html
> * GNOME evolution
>
> * Patches which are status: RFC
>
> * sway
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02345.html
> * debbugs (currently debbuging this, but comments are welcome)
> https://lists.gnu.org/archive/html/guix-devel/2017-01/msg02110.html
>
>
>
>
> [0]: https://pagure.io/guix-dev
> --
> ng0 . https://www.inventati.org/patternsinthechaos/
>
--
next prev parent reply other threads:[~2017-02-02 4:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-02 0:26 Structured list of my patches ng0
2017-02-02 4:05 ` Pjotr Prins [this message]
2017-02-02 9:37 ` ng0
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=20170202040500.GA1967@mail.thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=contact.ng0@cryptolab.net \
--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).