From: Steve Kenton <skenton@ou.edu>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 1/1] tovid: new package
Date: Wed, 18 Mar 2015 12:21:33 -0500 [thread overview]
Message-ID: <5509B41D.8040300@ou.edu> (raw)
In-Reply-To: <20150318174714.2e552220@free-electrons.com>
On 03/18/2015 11:47 AM, Thomas Petazzoni wrote:
> Dear Steve Kenton,
>
> Essentially, anything that isn't obvious generally needs a comment
> somewhere :-)
Understood
>
>>>> +TOVID_SITE = http://tovid.googlecode.com/svn/trunk/tovid
>>>
>>> Google Code is closing. Is there a better location for this project? Or
>>> is the project planning to move to some other place in the near future ?
>> Did not know that, will investigate.
>
> Well, I think it's fine for now, the source URL can always be changed
> later when the project moves elsewhere. There have been some changes
> recently (today, yesterday, etc.) so the project seems to be maintained.
Here's what the maintainer had to say in a post yesterday:
"As well google code is shutting down, so I am in process of moving to a
new repo. More news to follow re this."
>
> BTW, I don't remember if I asked: why would you want to run something
> such as tovid on an embedded system? What's the final use case?
Rack mount video system, records and burns dvds on the fly.
Steve
>
> Thanks,
>
> Thomas
>
next prev parent reply other threads:[~2015-03-18 17:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-18 15:15 [Buildroot] [PATCH v3 1/1] tovid: new package Steve Kenton
2015-03-18 15:46 ` Thomas Petazzoni
2015-03-18 16:10 ` Steve Kenton
2015-03-18 16:47 ` Thomas Petazzoni
2015-03-18 17:21 ` Steve Kenton [this message]
2015-03-19 8:17 ` Thomas Petazzoni
2015-03-19 15:29 ` Steve Kenton
2015-03-19 15:33 ` Thomas Petazzoni
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=5509B41D.8040300@ou.edu \
--to=skenton@ou.edu \
--cc=buildroot@busybox.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