From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libev: fix download URL
Date: Mon, 29 May 2017 21:54:15 +0200 [thread overview]
Message-ID: <20170529215415.39d9e8a3@free-electrons.com> (raw)
In-Reply-To: <20170528204057.28697-1-bernd.kuhls@t-online.de>
Hello,
On Sun, 28 May 2017 22:40:57 +0200, Bernd Kuhls wrote:
> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de>
> ---
> package/libev/libev.mk | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Applied to master, thanks. Could you contact the upstream developer to
ask him to stop moving the tarballs around? It is really annoying that
the latest version is available in http://dist.schmorp.de/libev/, and
then gets moved to http://dist.schmorp.de/libev/Attic/ as soon as a
newer version is released.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-29 19:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-28 20:40 [Buildroot] [PATCH 1/1] package/libev: fix download URL Bernd Kuhls
2017-05-29 19:54 ` Thomas Petazzoni [this message]
2017-05-29 19:59 ` Bernd Kuhls
2017-06-01 14:29 ` 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=20170529215415.39d9e8a3@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