From: Jiri Slaby <jirislaby@gmail.com>
To: Oliver Schinagl <oliver+list@schinagl.nl>
Cc: linux-media <linux-media@vger.kernel.org>,
pfister@linuxtv.org, adq_dvb@lidskialf.net, js@linuxtv.org,
cus@fazekas.hu, mws@linuxtv.org, jmccrohan@gmail.com,
shaulkr@gmail.com, mkrufky@linuxtv.org, mchehab@redhat.com,
lubomir.carik@gmail.com,
Christoph Pfister <christophpfister@gmail.com>
Subject: Re: [RFC] Initial scan files troubles and brainstorming
Date: Mon, 07 Jan 2013 11:46:16 +0100 [thread overview]
Message-ID: <50EAA778.6000307@gmail.com> (raw)
In-Reply-To: <50D0E7A7.90002@schinagl.nl>
On 12/18/2012 11:01 PM, Oliver Schinagl wrote:
> Unfortunatly, I have had zero replies.
Hmm, it's sad there is a silence in this thread from linux-media guys :/.
> So why bring it up again? On 2012/11/30 Jakub Kasprzycki provided us
> with updated polish DVB-T frequencies for his region. This has yet to be
> merged, almost 3 weeks later.
I sent a patch for cz data too:
https://patchwork.kernel.org/patch/1844201/
> I'll quickly repeat why I think this approach would be quite reasonable.
>
> * dvb-apps binary changes don't result in unnecessary releases
> * frequency updates don't result in unnecessary dvb-app releases
> * Less strict requirements for commits (code reviews etc)
Well the code should be reviewed still. See commit a2e96055db297 in your
repo, it's bogus. The freq added is in kHz instead of MHz.
> * Possibly easier entry for new submitters
> * much easier to package (tag it once per month if an update was)
> * Separate maintainer possible
> * just seems more logical to have it separated ;)
The downside is you have to change the URL in kaffeine sources as
kaffeine generates its scan file from that repo (on the server side and
the client downloads then http://kaffeine.kde.org/scanfile.dvb.qz).
> This obviously should find a nice home on linuxtv where it belongs!
At best.
> Here is my personal repository with the work I mentioned done.
> git://git.schinagl.nl/dvb_frequency_scanfiles.git
>
> If an issue is that none of the original maintainers are not looking
> forward to do the job, I am willing to take maintenance on me for now.
Ping? Anybody? I would help with that too as I hate resending patches.
But the first step I would do is a conversion to GIT. HG is demented to
begin with.
--
js
next prev parent reply other threads:[~2013-01-07 10:53 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-18 11:26 [RFC] Initial scan files troubles and brainstorming Oliver Schinagl
2012-12-18 22:01 ` Oliver Schinagl
[not found] ` <50D0FAE3.5000103@gmail.com>
2012-12-19 8:54 ` Oliver Schinagl
2013-01-07 10:46 ` Jiri Slaby [this message]
2013-01-07 12:48 ` Oliver Schinagl
2013-01-08 20:01 ` Johannes Stezenbach
2013-01-09 9:43 ` Oliver Schinagl
2013-01-09 10:41 ` Mauro Carvalho Chehab
2013-01-09 11:08 ` Michael Krufky
2013-01-09 14:41 ` Mauro Carvalho Chehab
2013-01-09 14:48 ` kaffeine.kde.org/scanfile.dvb.qz is obsolete [was: [RFC] Initial scan files troubles and brainstorming] Jiri Slaby
2013-01-10 16:33 ` Christoph Pfister
2013-01-10 17:40 ` [RFC] Initial scan files troubles and brainstorming Manu Abraham
2013-01-10 18:37 ` Jiri Slaby
2013-01-10 18:46 ` Manu Abraham
2013-01-10 18:56 ` Michael Krufky
2013-01-10 19:03 ` Jiri Slaby
2013-01-10 19:04 ` Manu Abraham
2013-01-10 20:15 ` Oliver Schinagl
2013-01-10 20:25 ` Manu Abraham
2013-01-10 20:32 ` Jiri Slaby
2013-01-10 20:38 ` Manu Abraham
2013-01-10 20:41 ` Jiri Slaby
2013-01-10 20:42 ` Jiri Slaby
2013-01-10 23:19 ` Oliver Schinagl
2013-01-10 20:49 ` Manu Abraham
2013-01-10 21:22 ` Jiri Slaby
2013-01-10 21:28 ` Manu Abraham
2013-01-10 20:55 ` Oliver Schinagl
2013-01-11 1:12 ` Jonathan McCrohan
2013-01-11 8:10 ` Legallity of dtv-scan-tables Was: " Oliver Schinagl
2013-01-11 12:23 ` Mauro Carvalho Chehab
2013-01-11 14:10 ` Benny Amorsen
2013-01-11 14:53 ` Mauro Carvalho Chehab
2013-01-24 14:16 ` Oliver Schinagl
2013-01-10 20:37 ` Mauro Carvalho Chehab
2013-01-10 20:43 ` Manu Abraham
2013-01-10 20:36 ` Manu Abraham
2013-01-10 19:02 ` Jiri Slaby
2013-01-10 19:08 ` Manu Abraham
2013-01-10 19:11 ` Jiri Slaby
2013-01-10 19:16 ` Manu Abraham
2013-01-10 20:04 ` Mauro Carvalho Chehab
2013-01-10 20:19 ` Manu Abraham
2013-01-10 20:32 ` Manu Abraham
2013-01-10 20:51 ` Oliver Schinagl
2013-01-10 21:04 ` Manu Abraham
2013-01-10 22:11 ` Mauro Carvalho Chehab
2013-01-10 22:57 ` Oliver Schinagl
2013-01-11 12:39 ` Mauro Carvalho Chehab
2013-01-11 13:37 ` Jiri Slaby
2013-06-03 17:21 ` daily tarballs of dtv-scan-tables - was " Mauro Carvalho Chehab
2013-06-03 20:48 ` Oliver Schinagl
[not found] ` <20130109084425.7ac6dc50@redhat.com>
[not found] ` <50ED4CEB.3050303@schinagl.nl>
[not found] ` <20130109100438.748924c8@redhat.com>
[not found] ` <50ED616D.1070108@schinagl.nl>
[not found] ` <20130109123758.7d91ab5a@redhat.com>
2013-01-09 14:44 ` Oliver Schinagl
2013-01-09 15:01 ` Mauro Carvalho Chehab
2013-01-09 15:05 ` Oliver Schinagl
2013-01-09 11:07 ` Johannes Stezenbach
2013-01-07 12:53 ` Christoph Pfister
2013-01-07 16:24 ` Manu Abraham
2013-01-07 22:44 ` Jonathan McCrohan
2013-01-08 8:06 ` Oliver Schinagl
2013-01-08 19:40 ` Johannes Stezenbach
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=50EAA778.6000307@gmail.com \
--to=jirislaby@gmail.com \
--cc=adq_dvb@lidskialf.net \
--cc=christophpfister@gmail.com \
--cc=cus@fazekas.hu \
--cc=jmccrohan@gmail.com \
--cc=js@linuxtv.org \
--cc=linux-media@vger.kernel.org \
--cc=lubomir.carik@gmail.com \
--cc=mchehab@redhat.com \
--cc=mkrufky@linuxtv.org \
--cc=mws@linuxtv.org \
--cc=oliver+list@schinagl.nl \
--cc=pfister@linuxtv.org \
--cc=shaulkr@gmail.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;
as well as URLs for NNTP newsgroup(s).