mirror of
https://github.com/openembedded/meta-openembedded.git
synced 2026-06-14 17:59:59 +00:00
Wang Mingyu
284a67d829
Changelog:
============
- Various spelling corrections.
- Fix issue where following links while doing JSON output would lead to
incorrect JSON output.
- Fix issue where .info patterns relative to the .info file that did not use
a wildcard for matching the prefix were not matching files properly.
- Added support for making trees from tab indented files (--fromtabfile)
- Fix buffer overflow in listdir() when file names are allowed to be longer
than 256 characters (like when using fromfile.)
- If when attempting to open a .gitignore or .info file from a top level
directory and failing, recursively check the parents for such a file. This
stops when successful at opening such a file. This behavior might in the
future be modified to open all such files in all parents to until root is
reached.
- Fix issue where tree would never descend (-l) a symbolic link when a full
tree is gathered (--du/matchdirs/prune)
Signed-off-by: Wang Mingyu <wangmy@fujitsu.com>
Signed-off-by: Khem Raj <raj.khem@gmail.com>
meta-oe ======= This layer depends on: URI: git://github.com/openembedded/openembedded-core.git branch: master luajit recipe requires host compiler to be able to generate 32bit code when target is 32bit e.g. arm, so ensure that $CC -m32 is functional on build host, if building this recipe, needed packages to fullfit this might have different names on different host distributions e.g. on archlinux based distributions install prerequisites like below pacman -S lib32-gcc-libs lib32-glibc Ubuntu sudo apt-get install gcc-multilib linux-libc-dev:i386 Send pull requests to openembedded-devel@lists.openembedded.org with '[meta-oe]' 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-oe][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: Khem Raj <raj.khem@gmail.com>