From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] libnl: bump to version 2.0
Date: Wed, 27 Apr 2011 13:26:56 +0200 [thread overview]
Message-ID: <87liywylxb.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4DB7D29E.5000101@visionsystems.de> (Yegor Yefremov's message of "Wed, 27 Apr 2011 10:23:58 +0200")
>>>>> "Yegor" == Yegor Yefremov <yegor_sub1@visionsystems.de> writes:
Out of interest, how did you create this patch? It doesn't have the nice
diffstat overview like git format-patch normally creates.
Yegor> Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com>
Yegor> Index: b/package/libnl/libnl.mk
Yegor> ===================================================================
Yegor> --- a/package/libnl/libnl.mk 2011-04-26 02:04:14.206276675 -0700
Yegor> +++ b/package/libnl/libnl.mk 2011-04-26 03:29:21.934275959 -0700
Yegor> @@ -4,10 +4,11 @@
Yegor> #
Yegor> #############################################################
Yegor> -LIBNL_VERSION = 1.1
Yegor> +LIBNL_VERSION = 2.0
I see there's already a libnl-3.0, is there any reason why you stick
with 2.0?
Yegor> LIBNL_SOURCE = libnl-$(LIBNL_VERSION).tar.gz
Yegor> -LIBNL_SITE = http://distfiles.gentoo.org/distfiles
Yegor> +LIBNL_SITE = http://www.infradead.org/~tgr/libnl/files/
Yegor> LIBNL_INSTALL_STAGING = YES
Yegor> +LIBNL_AUTORECONF = YES
Why? You don't seem to be patching any auto* stuff?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-04-27 11:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-27 8:23 [Buildroot] [PATCH] libnl: bump to version 2.0 Yegor Yefremov
2011-04-27 11:26 ` Peter Korsgaard [this message]
2011-04-27 12:51 ` Yegor Yefremov
2011-04-27 12:56 ` Peter Korsgaard
2011-04-27 12:58 ` Yegor Yefremov
2011-04-27 13:41 ` Gustavo Zacarias
2011-04-28 7:26 ` Yegor Yefremov
2011-04-28 12:17 ` Gustavo Zacarias
2011-04-28 12:26 ` Yegor Yefremov
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=87liywylxb.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.