From: Douglas Schilling Landgraf <dougsland@gmail.com>
To: hermann pitton <hermann-pitton@arcor.de>
Cc: Hans Verkuil <hverkuil@xs4all.nl>,
linux-media@vger.kernel.org, hdegoede@redhat.com,
Devin Heitmueller <dheitmueller@kernellabs.com>
Subject: Re: v4l-utils: i2c-id.h and alevt
Date: Thu, 11 Mar 2010 11:14:19 -0300 [thread overview]
Message-ID: <4B98FABB.1040605@gmail.com> (raw)
In-Reply-To: <1268197457.3199.17.camel@pc07.localdom.local>
On 03/10/2010 02:04 AM, hermann pitton wrote:
> Hi Hans, both,
>
> Am Dienstag, den 09.03.2010, 08:48 +0100 schrieb Hans Verkuil:
>> It's nice to see this new tree, that should be make it easier to develop
>> utilities!
>>
>> After a quick check I noticed that the i2c-id.h header was copied from the
>> kernel. This is not necessary. The only utility that includes this is v4l2-dbg
>> and that one no longer needs it. Hans, can you remove this?
>>
>> The second question is whether anyone would object if alevt is moved from
>> dvb-apps to v4l-utils? It is much more appropriate to have that tool in
>> v4l-utils.
>
> i wonder that this stays such calm, hopefully a good sign.
>
> In fact alevt analog should come with almost every distribution, but the
> former alevt-dvb, named now only alevt, well, might be ok in some
> future, is enhanced for doing also dvb-t-s and hence there ATM.
>
>> Does anyone know of other unmaintained but useful tools that we might merge
>> into v4l-utils? E.g. xawtv perhaps?
>
> If for xawtv could be some more care, ships also since close to ever
> with alevtd, that would be fine, but I'm not sure we are talking about
> tools anymore in such case, since xawtv4x, tvtime and mpeg4ip ;) for
> example are also there and unmaintained.
>
I think would be nice to hear a word from Devin, which have been working in tvtime. Devin?
Cheers
Douglas
next prev parent reply other threads:[~2010-03-11 14:22 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-09 7:48 v4l-utils: i2c-id.h and alevt Hans Verkuil
2010-03-10 5:04 ` hermann pitton
2010-03-11 14:14 ` Douglas Schilling Landgraf [this message]
2010-03-11 14:31 ` Devin Heitmueller
2010-03-12 7:27 ` Hans Verkuil
2010-03-12 15:21 ` Devin Heitmueller
2010-03-12 15:38 ` Hans de Goede
2010-03-12 15:40 ` Hans de Goede
2010-03-12 16:20 ` Manu Abraham
2010-03-12 19:10 ` v4l-utils, dvb-utils, xawtv and alevt (was: v4l-utils: i2c-id.h and alevt) Chicken Shack
2010-03-13 6:51 ` v4l-utils, dvb-utils, xawtv and alevt Hans de Goede
2010-03-13 10:15 ` Chicken Shack
2010-03-13 12:34 ` Hans de Goede
2010-03-13 13:43 ` Chicken Shack
2010-03-14 5:39 ` hermann pitton
2010-03-14 11:13 ` Chicken Shack
2010-03-14 14:38 ` Aw: " hermann-pitton
2010-03-12 15:55 ` v4l-utils: i2c-id.h " Hans de Goede
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=4B98FABB.1040605@gmail.com \
--to=dougsland@gmail.com \
--cc=dheitmueller@kernellabs.com \
--cc=hdegoede@redhat.com \
--cc=hermann-pitton@arcor.de \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox