All of lore.kernel.org
 help / color / mirror / Atom feed
From: Oliver Schinagl <oliver+list@schinagl.nl>
To: linux-media <linux-media@vger.kernel.org>
Subject: [DTV Tables] Now also on github.
Date: Fri, 12 Jul 2013 09:12:19 +0200	[thread overview]
Message-ID: <51DFAC53.8000301@schinagl.nl> (raw)

Hey all,

since I hadn't received any comment in the previous message (which was a 
reply only) I thought i get this through the list as well.

I have created a github repostiory [0] for the dtv-tables so that it is 
easier for people to fork and upstream new data.

I'm not a fan to using github and not having patches submitted to me/the 
mailing list, but this isn't source code, but data that I feel is 
important to have in the tree as fast as possible.

I wouldn't be surprised that at some point some random manufacturer puts 
a reference to this tree into their system, be it closed or open, and it 
would be nice that our tables be as up to date as possible.

The best workflow I can think of, is that I will merge requests on 
github, pull them to my local repository, send the commit to the ML list 
before pushing it to linuxtv.org, but if better ideas arise, I'm all ears.

Oliver

                 reply	other threads:[~2013-07-12  7:14 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=51DFAC53.8000301@schinagl.nl \
    --to=oliver+list@schinagl.nl \
    --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.