From: Jaroslav Kysela <perex@perex.cz>
To: John Spencer <maillist-alsa@barfooze.de>
Cc: Joe Perches <joe@perches.com>, Takashi Iwai <tiwai@suse.de>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: [RFC PATCH] MAINTAINERS: Remove Jaroslav Kysela
Date: Fri, 08 Nov 2013 12:38:36 +0100 [thread overview]
Message-ID: <527CCD3C.7000207@perex.cz> (raw)
In-Reply-To: <527CC315.7080701@barfooze.de>
Date 8.11.2013 11:55, John Spencer wrote:
> Jaroslav Kysela wrote:
>> Date 7.11.2013 21:04, Joe Perches wrote:
>>> Jaroslav hasn't acked or signed a patch in quite awhile.
>>
>> It does not mean that I'm not willing to continue the kernel code
>> maintenance when Takashi is offline. Keep me in. You may reorder M: lines.
>
> Jaroslav, care to answer my question i asked you in July?
>
> http://mailman.alsa-project.org/pipermail/alsa-devel/2013-July/064402.html
>
> it's important, as it's one of the last hurdles preventing alsa-lib from
> compiling out-of-the-box against musl libc.
http://git.alsa-project.org/?p=alsa-lib.git;a=commitdiff;h=7d06b3ed9fda0220c2863ee20acd10c32cf313fd
Anyway, it's better to send a patch as Takashi suggested.
Jaroslav
--
Jaroslav Kysela <perex@perex.cz>
Linux Kernel Sound Maintainer
ALSA Project; Red Hat, Inc.
next prev parent reply other threads:[~2013-11-08 11:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-07 20:04 [RFC PATCH] MAINTAINERS: Remove Jaroslav Kysela Joe Perches
2013-11-08 7:28 ` Jaroslav Kysela
2013-11-08 7:28 ` Jaroslav Kysela
2013-11-08 10:55 ` John Spencer
2013-11-08 11:07 ` _POSIX_C_SOURCE (Was: [RFC PATCH] MAINTAINERS: Remove Jaroslav Kysela) Takashi Iwai
2013-11-08 11:38 ` Jaroslav Kysela [this message]
2013-11-08 11:54 ` [RFC PATCH] MAINTAINERS: Remove Jaroslav Kysela Joe Perches
2013-11-08 8:24 ` Richard Weinberger
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=527CCD3C.7000207@perex.cz \
--to=perex@perex.cz \
--cc=alsa-devel@alsa-project.org \
--cc=joe@perches.com \
--cc=maillist-alsa@barfooze.de \
--cc=tiwai@suse.de \
/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.
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.