From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Brandon Philips <brandon@ifup.org>
Cc: Linux and Kernel Video <video4linux-list@redhat.com>,
linux-dvb <linux-dvb@linuxtv.org>
Subject: Re: Hauppauge HVR1400 DVB-T support / XC3028L
Date: Tue, 22 Apr 2008 18:46:19 -0300 [thread overview]
Message-ID: <20080422184619.7186db90@gaivota> (raw)
In-Reply-To: <20080422193342.GN7392@plankton.ifup.org>
On Tue, 22 Apr 2008 12:33:42 -0700
Brandon Philips <brandon@ifup.org> wrote:
> On 12:22 Tue 22 Apr 2008, Mauro Carvalho Chehab wrote:
> > On Mon, 21 Apr 2008 20:44:49 -0700
> > Brandon Philips <brandon@ifup.org> wrote:
> > > On 23:26 Mon 21 Apr 2008, Steven Toth wrote:
> > > > I've passed some patches to Mauro that add support for the Hauppauge
> > > > HVR1400 Expresscard in DVB-T mode. (cx23885 bridge, dib7000p
> > > > demodulator and the xceive xc3028L silicon tuner)
> > > >
> > > > If you're interested in testing then wait for the patches to appear
> > > > in the http://linuxtv.org/hg/v4l-dvb tree.
> > > >
> > > > You'll need to download firmware from
> > > > http://steventoth.net/linux/hvr1400
> > > >
> > > > Post any questions or issues here.
> > >
> > > Could you post the patches to the lists for review? CC'ing both
> > > linux-dvb@linuxtv.org and video4linux-list@redhat.com is appropriate.
> > >
> > > It is really difficult staying on top of V4L with private trees and
> > > private mails going around :(
> >
> > The better way for you to track about committed patches is what's described on
> > item 5: "Knowing about newer patches committed at master hg repository", of
> > http://linuxtv.org/hg/v4l-dvb/raw-file/tip/README.patches.
> >
> > Basically, if you subscribe to linuxtv-commits ML[1], you'll receive an email for
> > every newly committed changeset.
>
> I think the list is broken. The archives haven't received anything
> since Feb. 2008... http://www.linuxtv.org/pipermail/linuxtv-commits/
The archive is disabled. The list should contain just the patches that are
already stored at the tree. Archiving the emails will just spend some space for
a duplicated info. So, I think Johannes disabled it to save some space.
> I also signed up but haven't receive emails from anything you merged a
> few hours ago.
This is weird. I've checked: you're subscribed. Did you subscribe only today?
Maybe there weren't any new commits after your subscription.
> I am just concerned about the v4l-dvb-maintainers list being too private
> and private trees not getting enough review before going into mainline.
> linuxtv-commits may help.
I think it is a good idea that the pull requests would be also c/c to V4L
and/or DVB ML.
Cheers,
Mauro
--
video4linux-list mailing list
Unsubscribe mailto:video4linux-list-request@redhat.com?subject=unsubscribe
https://www.redhat.com/mailman/listinfo/video4linux-list
next prev parent reply other threads:[~2008-04-22 21:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-22 3:26 Hauppauge HVR1400 DVB-T support / XC3028L Steven Toth
2008-04-22 3:44 ` Brandon Philips
2008-04-22 13:03 ` Steven Toth
2008-04-22 15:22 ` Mauro Carvalho Chehab
2008-04-22 19:33 ` Brandon Philips
2008-04-22 21:46 ` Mauro Carvalho Chehab [this message]
2008-04-22 13:07 ` [linux-dvb] " Jean-Michel Brünn
2008-04-22 14:28 ` Steven Toth
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=20080422184619.7186db90@gaivota \
--to=mchehab@infradead.org \
--cc=brandon@ifup.org \
--cc=linux-dvb@linuxtv.org \
--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