From: Oliver Schinagl <oliver+list@schinagl.nl>
To: Jonathan McCrohan <jmccrohan@gmail.com>,
linux-media <linux-media@vger.kernel.org>
Subject: Re: dtv-scan-tables updates
Date: Tue, 09 Jul 2013 08:33:26 +0200 [thread overview]
Message-ID: <51DBAEB6.8000004@schinagl.nl> (raw)
In-Reply-To: <51DB4759.603@gmail.com>
On 09-07-13 01:12, Jonathan McCrohan wrote:
> Hi Oliver,
>
> I was just taking a look around github, and noticed that some people
> have forked their own versions of dtv-scan-tables on there.
*sigh*
>
> There appear to be some worthwhile contributions there that have not
> been upstreamed. [1],[2],[3],[4],[5]
Will investigate those and see whats there
>
> It might be a good idea to contact the authors in question to ask if
> they are okay with their contributions being upstreamed. It might also
> be an idea to set up an 'official' github mirror of the dtv-scan-tables
> tree. It might make it easier for contributors to upstream their work
> using github's pull request workflow rather than dealing with
> git-send-email etc?
I agree that its much easier to deal with, especially for external
parties that are unfamiliar with git. I suppose the windows tools make
it much easier for people to do things, without them even knowing what
they do? I never used them so can't be sure.
>
> Just an idea.
Its not a bad idea, and we're not directly dealing with actual code, so
the dtv changes could be done that way. Now its time for people to
disagree and tell us why it's a bad idea :)
>
> Jon
>
> [1]
> https://github.com/hiroshiyui/dvb-apps/commit/c2e3b732cae849a151c27929204c20ac40b920d0.patch
>
> [2]
> https://github.com/vlalov/dtv-scan-tables/commit/682aca38813e6731c5305fe6eb3aa9c05b2eb931.patch
>
> [3]
> https://github.com/crazycat69/dtv-scan-tables/commit/5966b7da708753130c815cb078875b58b18d9ddf.patch
>
> [4]
> https://github.com/crazycat69/dtv-scan-tables/commit/1c1942782c10016709189bb3675fc06fdf684609.patch
>
> [5]
> https://github.com/crazycat69/dtv-scan-tables/commit/d826071cbdf09d8f3090af148b72a5af820b75bb.patch
>
parent reply other threads:[~2013-07-09 6:33 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <51DB4759.603@gmail.com>]
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=51DBAEB6.8000004@schinagl.nl \
--to=oliver+list@schinagl.nl \
--cc=jmccrohan@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.