public inbox for linux-media@vger.kernel.org
 help / color / mirror / Atom feed
From: "Lothar Brendel" <l.brendel@goldmail.de>
To: <video4linux-list@redhat.com>
Subject: help
Date: Thu, 21 Feb 2008 09:25:10 +0100	[thread overview]
Message-ID: <017a01c87463$466cd120$4db2a8c0@MultiOcke> (raw)
In-Reply-To: 20080220170012.C9E168E0292@hormel.redhat.com

video4linux-list-request@redhat.com wrote:
>> Send video4linux-list mailing list submissions to
>> video4linux-list@redhat.com
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>> https://www.redhat.com/mailman/listinfo/video4linux-list
>> or, via email, send a message with subject or body 'help' to
>> video4linux-list-request@redhat.com
>> 
>> You can reach the person managing the list at
>> video4linux-list-owner@redhat.com
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of video4linux-list digest..."
>> 
> 
> 
> 
>> Today's Topics:
>> 
>>   1. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: When xc3028/xc2028 will be supported? (Daniel Gimpelevich)
>>   2. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: When xc3028/xc2028 will be supported? (D?niel Fraga)
>>   3. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: When xc3028/xc2028 will be supported? (Mauro Carvalho
>> Chehab) 
>>   4. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: Wh en xc3028/xc2028 will be supported? (mkrufky@linuxtv.org)
>>   5. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: When xc3028/xc2028 will be supported? (Mauro Carvalho
>> Chehab) 
>>   6. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: Wh en xc3028/xc2028 will be supported? (Mauro Carvalho
>> Chehab) 
>>   7. Re: [linux-dvb] [patch] support for key repeat with dib0700
>>      ir receiver (hermann pitton)
>>   8. Re: [linux-dvb] auto detection of Flytv duo/hybrid and
>>      pci/cardbus confusion (hermann pitton)
>>   9. Re: [EXPERIMENTAL] cx88+xc3028 - tests are required - was:
>>      Re: When xc3028/xc2028 will be supported? (D?niel Fraga)
>>  10. Supported device? (Lyal Collins)
>>  11. Re: NULL pointer dereference while loading saa7133 on
>>      2.6.25-rc2 (mkrufky@linuxtv.org)
>> 
> 
> 
> 
>> --
>> video4linux-list mailing list
>> Unsubscribe
>> mailto:video4linux-list-request@redhat.com?subject=unsubscribe
>> https://www.redhat.com/mailman/listinfo/video4linux-list 

--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list

       reply	other threads:[~2008-02-21  8:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080220170012.C9E168E0292@hormel.redhat.com>
2008-02-21  8:25 ` Lothar Brendel [this message]
     [not found] <20081205170026.821496198E3@hormel.redhat.com>
2008-12-05 17:24 ` help Brian Rosenberger
2011-10-14 16:21 help Mario Torres
  -- strict thread matches above, loose matches on Subject: below --
2011-10-14 16:22 help Mario Torres
2011-10-17 23:50 help Mario Torres
2018-05-06 19:28 help Richard Lee
2019-02-06  5:26 help John Klug

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='017a01c87463$466cd120$4db2a8c0@MultiOcke' \
    --to=l.brendel@goldmail.de \
    --cc=video4linux-list@redhat.com \
    /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