All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Christian Hewitt <christianshewitt@gmail.com>
Cc: linux-media@vger.kernel.org
Subject: Re: RESEND: RFC: dtv-scan-tables: plans to upstream changes from Tvheadend.org
Date: Tue, 30 Jan 2024 17:41:44 +0100	[thread overview]
Message-ID: <20240130174144.64f0f5b6@coco.lan> (raw)
In-Reply-To: <3880598D-563D-4A40-A7E4-0AE9C655443F@gmail.com>

Hi Christian

Em Mon, 29 Jan 2024 11:30:26 +0400
Christian Hewitt <christianshewitt@gmail.com> escreveu:

> Resending due to no response since 12th Jan:
> 
> Hello Mauro,
> 
> The Tvheadend project bundles dtv-scan-tables in our deb/rpm packages. We have
> our own repo for them; an unmaintained fork of someone else’s unmaintained fork
> of the upstream linuxtv repo https://git.linuxtv.org/dtv-scan-tables.git.

Maintaining forks are hard :-)

> 
> To improve things for everyone we are planning to retool around the linuxtv.org
> repo and would like to sync/upstream the differences to you. The current diff
> can be seen here: 
> 
> https://github.com/chewitt/dtv-scan-tables/compare/master...tvheadend

Wow! diff sounds huge!

> The main challenges are, a) scrappy descriptions, b) contributor real-names and
> email are missing from most of them, c) multiple contributors to the same files
> over time.
> 
> I was thinking to send a series with one patch for each country-code to reduce
> the number of patches to review, with links to original pull-requests in patch
> descriptions to provide attribution to original changes, and any other info
> like URLs added to files as comments if the links still work.

Works for me. I also have a couple of scripts here to help updating from 
https://www.lyngsat.com/ and from a Brazilian site for ISDB-T. 

I'm run them right now to update dvb-s and isdb-t channels. With that,
it probably won't make sense for you to update dvb-s/s2 and isdb-t channels
from tvheadend fork.

Still, we have gaps on dvb-c/t/t2 and atsc.

> Moving forwards we plan to add a PR template to our GitHub repo that encourages
> patches to be sent directly to the linux-media list; or for contributors to
> provide us with real-name/email for attribution so we can upstream patches on
> their behalf, or remain anonymous but give permission for patches to be sent
> under Tvheadend attribution (likely as myself).

Makes sense. Once we get this in sync, we can discuss further about how to
keep it updated.

> Would my per-country-code patch suggestion work for you? or how would you like
> us to handle the changes?

Per-country-code seems good to me, but the sync has to happen on both
directions, as we've been receiving channels upstream too. Checking what
is the more updated version can be harsh, as you'll need to check it patch
per patch.

> 
> Regards, Christian
> chewitt@tvheadend.org
> 
> NB: The pending patch from Simon Liddicott [0] reduces the diff. Could that be
> merged soon?
> 
> [0] https://patchwork.linuxtv.org/project/linux-media/patch/20230216010528.5921-1-simon@liddicott.com/

Merged, thanks!

Thanks,
Mauro

      reply	other threads:[~2024-01-30 16:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-29  7:30 RESEND: RFC: dtv-scan-tables: plans to upstream changes from Tvheadend.org Christian Hewitt
2024-01-30 16:41 ` Mauro Carvalho Chehab [this message]

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=20240130174144.64f0f5b6@coco.lan \
    --to=mchehab@kernel.org \
    --cc=christianshewitt@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.