From: "Jörg Krause" <jkrause@posteo.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/libnfs: bump to version 1.9.5
Date: Wed, 15 Oct 2014 11:15:46 +0200 [thread overview]
Message-ID: <543E3B42.7030309@posteo.de> (raw)
In-Reply-To: <543E2EC6.1000205@trzebnica.net>
Hi Jerzy,
On 10/15/2014 10:22 AM, Jerzy Grzegorek wrote:
> Hi J?rg,
>
>> * bump to version 1.9.5
>> * fix version and site symbol
>>
>> Signed-off-by: J?rg Krause <jkrause@posteo.de>
>> ---
>> package/libnfs/libnfs.mk | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>>
>> diff --git a/package/libnfs/libnfs.mk b/package/libnfs/libnfs.mk
>> index a17d8c3..f2d7938 100644
>> --- a/package/libnfs/libnfs.mk
>> +++ b/package/libnfs/libnfs.mk
>> @@ -4,8 +4,8 @@
>> #
>> ################################################################################
>> -LIBNFS_VERSION = libnfs-1.8.0
>> -LIBNFS_SITE = $(call github,sahlberg,libnfs,$(LIBNFS_VERSION))
>> +LIBNFS_VERSION = 1.9.5
>> +LIBNFS_SITE = $(call github,sahlberg,libnfs,libnfs-$(LIBNFS_VERSION))
>
> Since the tag of libnfs version 1.9.5 is libnfs-1.9.5
> so this should be:
>
> +LIBNFS_VERSION = libnfs-1.9.5
> +LIBNFS_SITE = $(call github,sahlberg,libnfs,$(LIBNFS_VERSION))
>
You're right, the tag is libnfs-1.9.5. I didn't liked that libnfs was
build in libnfs-libnfs-1.9.5 (now it builds in libnfs-1.9.5). But I've
seen in the manual that version should be a tag or a commit. I will fix
this.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20141015/d16c4fda/attachment.html>
next prev parent reply other threads:[~2014-10-15 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-15 7:25 [Buildroot] [PATCH 1/1] package/libnfs: bump to version 1.9.5 Jörg Krause
2014-10-15 8:22 ` Jerzy Grzegorek
2014-10-15 9:15 ` Jörg Krause [this message]
2014-10-15 11:57 ` Arnout Vandecappelle
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=543E3B42.7030309@posteo.de \
--to=jkrause@posteo.de \
--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