Linux Media Controller development
 help / color / mirror / Atom feed
From: Andy Walls <awalls@md.metrocast.net>
To: Hans de Goede <hdegoede@redhat.com>, Hans Verkuil <hverkuil@xs4all.nl>
Cc: linux-media@vger.kernel.org, ivtv-devel@ivtvdriver.org
Subject: RFC: Move ivtv utilities and ivtv X video extension to v4l-utils
Date: Thu, 16 Sep 2010 18:58:45 -0400	[thread overview]
Message-ID: <1284677925.2056.27.camel@morgan.silverblock.net> (raw)

Hi Hans and Hans,

I'd like to move the source code maintained here:

http://ivtvdriver.org/svn/

to someplace where it may be less likely to suffer bit rot.
I was hoping the v4l-utils git repo would be an appropriate place.

Do either of you have any opinions on this?

If you think it would be acceptable, do you have a preference on where
they would be placed in the v4l-utils directory structure?

Thanks.

Regards,
Andy


             reply	other threads:[~2010-09-16 22:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-16 22:58 Andy Walls [this message]
2010-09-17  4:00 ` RFC: Move ivtv utilities and ivtv X video extension to v4l-utils Hans de Goede
2010-09-17  8:30 ` Hans Verkuil
2010-09-17 10:59   ` Andy Walls
2010-09-17 11:25     ` Hans Verkuil

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=1284677925.2056.27.camel@morgan.silverblock.net \
    --to=awalls@md.metrocast.net \
    --cc=hdegoede@redhat.com \
    --cc=hverkuil@xs4all.nl \
    --cc=ivtv-devel@ivtvdriver.org \
    --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