meta-openembedded/meta-multimedia
Preeti Sachan 0342b7b6c3 fluidsynth: update SRC_URI to remove non-existing 2.2.x branch
Remove branch 2.2.x from SRC_URI as fluidsynth github removed the branch.
The SRCREV is on master branch.

Signed-off-by: Preeti Sachan <preeti.sachan@intel.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
(cherry picked from commit 534d04af48)
Signed-off-by: Scott Murray <scott.murray@konsulko.com>
Signed-off-by: Armin Kuster <akuster808@gmail.com>
2023-03-05 07:45:14 -05:00
..
classes Convert to new override syntax 2021-08-03 10:21:25 -07:00
conf layer.conf: change layer priority to match oe-core 2022-02-28 08:39:26 -08:00
licenses Alliance for Open Media: new library 2020-10-06 08:45:24 -07:00
recipes-connectivity recipes: Update LICENSE variable to use SPDX license identifiers 2022-03-04 17:41:45 -08:00
recipes-dvb tvheadend: Update to latest trunk 2022-04-13 19:21:41 -07:00
recipes-mkv recipes: Update LICENSE variable to use SPDX license identifiers 2022-03-04 17:41:45 -08:00
recipes-multimedia fluidsynth: update SRC_URI to remove non-existing 2.2.x branch 2023-03-05 07:45:14 -05:00
recipes-support srt: 1.4.3 -> 1.4.4 2022-04-06 20:25:33 -04:00
COPYING.MIT meta-multimedia: initial add 2012-02-24 13:53:17 +01:00
README meta-openemnedded: Add myself as kirkstone maintainer 2022-04-23 17:14:31 -07:00

This layer depends on:

URI: git://git.openembedded.org/openembedded-core
branch: kirkstone

URI: git://git.openembedded.org/meta-openembedded
layers: meta-oe
branch: kirkstone

Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-multimedia][kirkstone]' 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][kirkstone][PATCH'

You are encouraged to fork the mirror on github https://github.com/openembedded/meta-openembedded to share your patches, this is preferred for patch sets consisting of more than one patch. Other services like GitLab, 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.

Layer maintainer: Armin Kuster <akuster808@gmail.com>