From: ng0 <ng0@we.make.ritual.n0.is>
To: guix-devel@gnu.org
Subject: [PATCH] alsa-plugins, revision 3
Date: Mon, 31 Oct 2016 14:39:57 +0000 [thread overview]
Message-ID: <20161031143958.24208-1-ng0@we.make.ritual.n0.is> (raw)
In-Reply-To: <87r36yale0.fsf@elephly.net>
I tried to debug what's faulty about the two for-each here, but I don't find it.
Help welcome :)
next prev parent reply other threads:[~2016-10-31 14:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-29 14:43 [PATCH] alsa-plugins , revision 2 ng0
2016-10-29 14:43 ` [PATCH] gnu: Add alsa-plugins ng0
2016-10-29 21:35 ` Ricardo Wurmus
2016-10-31 14:39 ` ng0 [this message]
2016-10-31 14:39 ` ng0
2016-12-19 17:59 ` Kei Kebreau
2016-12-20 14:53 ` alsa-plugins, new version of patch ng0
2016-12-20 14:53 ` [PATCH] gnu: Add alsa-plugins ng0
2016-12-20 15:52 ` alsa-plugins, new version of patch Kei Kebreau
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=20161031143958.24208-1-ng0@we.make.ritual.n0.is \
--to=ng0@we.make.ritual.n0.is \
--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).