From: Lee Revell <rlrevell@joe-job.com>
To: Mark Salazar <markTheCoder@justmyself.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: [es18xx.c PATCH] #1/4 for Zoom Video - resolve common vs chipset specific mixer controls
Date: Mon, 26 Dec 2005 12:46:39 -0500 [thread overview]
Message-ID: <1135619199.8293.46.camel@mindpipe> (raw)
In-Reply-To: <43B02A0E.20401@justmyself.net>
On Mon, 2005-12-26 at 12:36 -0500, Mark Salazar wrote:
> Lee Revell wrote:
>
> >On Mon, 2005-12-26 at 10:44 -0500, Mark Salazar wrote:
> >> First of 4 es18xx.c patches culminating in Zoom Video support.
> >
> >All of these except the first are linewrapped and can't be applied.
> >
> >
>
> I surrender. Unable to make Thunderbird's wrapping function submit to
> my will I just attach my patch message and slink away.
Wow is Thunderbird really such garbage that this is impossible? It
would explain why we see so many line wrapped patches on LKML.
Someone should really follow up on this with the Mozilla developers.
Lee
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next prev parent reply other threads:[~2005-12-26 17:46 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-26 15:44 [es18xx.c PATCH] #1/4 for Zoom Video - resolve common vs chipset specific mixer controls Mark Salazar
2005-12-26 16:07 ` Lee Revell
2005-12-26 17:36 ` Mark Salazar
2005-12-26 17:46 ` Lee Revell [this message]
2006-01-02 14:22 ` Takashi Iwai
2006-01-08 23:01 ` Mark Salazar
2006-01-09 12:13 ` Takashi Iwai
2006-01-10 0:58 ` Mark Salazar
[not found] ` <s5hu0ccfgu6.wl%tiwai@suse.de>
2006-01-15 20:30 ` Mark Salazar
2006-01-16 11:43 ` Takashi Iwai
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=1135619199.8293.46.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=markTheCoder@justmyself.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox