uboot-tools: fix license issues
PATCH 1/1 uboot-tools: fix license issues
Fix license directory and filename change, fixes:
http://autobuild.buildroot.net/results/8c9/8c94c81fe74399c854de335329cf4942f8356fbe/
--- package/uboot-tools/uboot-tools.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
package/uboot-tools/uboot-tools.mk +1 -1
@@ -8,7 +8,7 @@ UBOOT_TOOLS_VERSION = 2013.10 UBOOT_TOOLS_SOURCE = u-boot-$(UBOOT_TOOLS_VERSION).tar.bz2 UBOOT_TOOLS_SITE = ftp://ftp.denx.de/pub/u-boot UBOOT_TOOLS_LICENSE = GPLv2+ -UBOOT_TOOLS_LICENSE_FILES = COPYING +UBOOT_TOOLS_LICENSE_FILES = Licenses/gpl-2.0.txt define UBOOT_TOOLS_BUILD_CMDS $(MAKE) -C $(@D) \
Signature · 1 line
1.8.1.5
Thomas Petazzoni
AppliedPATCH 1/1 uboot-tools: fix license issues
Dear Gustavo Zacarias,
Quoted 7 lines · Gustavo Zacarias
Fix license directory and filename change, fixes:
http://autobuild.buildroot.net/results/8c9/8c94c81fe74399c854de335329cf4942f8356fbe/Signed-off-by Gustavo Zacarias <[email protected]>--- package/uboot-tools/uboot-tools.mk | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to for-peter-2013.11, thanks!
For some reason, this patch was not in patchwork, not sure what happened, since I don't see it having been applied on master by Peter, unless I missed something.
Thanks!
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 uboot-tools: fix license issues
Quoted 3 lines · Thomas Petazzoni
For some reason, this patch was not in patchwork, not sure what happened, since I don't see it having been applied on master by Peter, unless I missed something.
Patchwork is acting up a little sometimes, for instance some patches that were applied by Peter were never marked as accepted (for instance the libpng disable tools patch IIRC).
Better keep an eye on it ;)
Regards.
PATCH 1/1 uboot-tools: fix license issues
Dear Gustavo Zacarias,
Quoted 9 lines · Gustavo Zacarias
Quoted 3 lines · Thomas Petazzoni
For some reason, this patch was not in patchwork, not sure what happened, since I don't see it having been applied on master by Peter, unless I missed something.
Patchwork is acting up a little sometimes, for instance some patches that were applied by Peter were never marked as accepted (for instance the libpng disable tools patch IIRC).
This is expected when Peter makes a small modification to the patch:
patchwork no longer recognizes the committed patch as being the same as the patch sitting in the queue.
However, a patch not committed and not visible in patchwork is a bit weird (except for patches that only rename files, because the patch contents are empty and patchwork doesn't understand that).
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com
PATCH 1/1 uboot-tools: fix license issues
Thomas, All,
On 2013-11-02 17:43 +0100, Thomas Petazzoni spake thusly:
Quoted 3 lines
However, a patch not committed and not visible in patchwork is a bit weird (except for patches that only rename files, because the patch contents are empty and patchwork doesn't understand that).
Actually, this last part is now wrong: patchwork should now recognise renames-only patches (since about two weeks now).
Regards,
Yann E. MORIN.
Signature · 6 lines
.-----------------.--------------------.------------------.--------------------. | Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: | | +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ | | +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no | | http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. | '------------------------------^-------^------------------^--------------------'
PATCH 1/1 uboot-tools: fix license issues
Dear Yann E. MORIN,
Quoted 7 lines · Yann E. MORIN
On 2013-11-02 17:43 +0100, Thomas Petazzoni spake thusly:
Quoted 3 lines
However, a patch not committed and not visible in patchwork is a bit weird (except for patches that only rename files, because the patch contents are empty and patchwork doesn't understand that).
Actually, this last part is now wrong: patchwork should now recognise renames-only patches (since about two weeks now).
Aaah, and this is actually true! The ngrep patches renaming patch was recognized by patchwork.
My bad,
Thomas
Signature · 3 lines
Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com