meta-openembedded/meta-multimedia
Jackie Huang b79176adb3 remove the unnecessary protocol parameters
It's not necessary to specify the protocol parameter when it's the
default protocol for the fetcher, e.g. the default protocol for
git fetcher it git, "protocol=git" isn't needed.

Signed-off-by: Jackie Huang <jackie.huang@windriver.com>
Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
2013-09-03 16:59:13 +02:00
..
conf meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
recipes-connectivity/gupnp recipes: Unify indentation 2013-04-15 16:23:17 +02:00
recipes-dvb recipes: Unify indentation 2013-04-15 16:23:17 +02:00
recipes-mediacentre/xbmc remove the unnecessary protocol parameters 2013-09-03 16:59:13 +02:00
recipes-mkv mkvtoolnix: inherit gettext and export RUBYLIB 2013-07-30 11:17:12 +02:00
recipes-multimedia remove the unnecessary protocol parameters 2013-09-03 16:59:13 +02:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README README: show github mirror URL in layer dependencies 2013-05-03 13:32:03 +02:00

This layer depends on:

URI: git://github.com/openembedded/oe-core.git
branch: master
revision: HEAD

URI: git://github.com/openembedded/meta-oe.git
layers: meta-oe, meta-ruby
branch: master
revision: HEAD

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia]' in the subject'

When sending single patches, please use something like:
'git send-email -M -1 --to openembedded-devel@lists.openembedded.org --subject-prefix=meta-multimedia][PATCH

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-oe/ to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like gitorious, repo.or.cz or self hosted setups are of course accepted as well, 'git fetch <remote>' works the same on all of them. We recommend github because it is free, easy to use, has been proven to be reliable and has a really good web GUI.

Main layer maintainers: Koen Kooi <koen@dominion.thruhere.net>
                        Martin Jansa <martin.jansa@gmail.com>