From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] libinput: add explicit event-gui handling
Date: Thu, 21 Apr 2016 23:39:13 +0200 [thread overview]
Message-ID: <20160421233913.7ed963dd@free-electrons.com> (raw)
In-Reply-To: <1461273652-8935-1-git-send-email-gustavo@zacarias.com.ar>
Hello,
On Thu, 21 Apr 2016 18:20:51 -0300, Gustavo Zacarias wrote:
> diff --git a/package/libinput/libinput.mk b/package/libinput/libinput.mk
> index 6d8b7b6..2954760 100644
> --- a/package/libinput/libinput.mk
> +++ b/package/libinput/libinput.mk
> @@ -7,13 +7,18 @@
> LIBINPUT_VERSION = 1.1.5
> LIBINPUT_SOURCE = libinput-$(LIBINPUT_VERSION).tar.xz
> LIBINPUT_SITE = http://www.freedesktop.org/software/libinput
> -LIBINPUT_LICENSE = MIT
> -LIBINPUT_LICENSE_FILES = COPYING
> -
> LIBINPUT_DEPENDENCIES = host-pkgconf libevdev mtdev udev
> LIBINPUT_INSTALL_STAGING = YES
> -
> +LIBINPUT_LICENSE = MIT
> +LIBINPUT_LICENSE_FILES = COPYING
You say in the commit log you're doing whitespace changes, but it seems
like the licence lines were moved down in the file. For what reason?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-04-21 21:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-21 21:20 [Buildroot] [PATCH 1/2] libinput: add explicit event-gui handling Gustavo Zacarias
2016-04-21 21:20 ` [Buildroot] [PATCH 2/2] libinput: bump to version 1.2.4 Gustavo Zacarias
2016-04-22 20:07 ` Peter Korsgaard
2016-04-21 21:39 ` Thomas Petazzoni [this message]
2016-04-22 13:31 ` [Buildroot] [PATCH 1/2] libinput: add explicit event-gui handling Gustavo Zacarias
2016-04-22 20:07 ` Peter Korsgaard
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=20160421233913.7ed963dd@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox