From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v1] wiringpi: bump version to 96344ff7125182989f98d3be8d111952a8f74e15 (the real 2.44)
Date: Wed, 11 Oct 2017 23:22:59 +0200 [thread overview]
Message-ID: <20171011232259.16581f9a@windsurf.lan> (raw)
In-Reply-To: <20171011222124.4d9e0756@gmx.net>
Hello,
On Wed, 11 Oct 2017 22:21:24 +0200, Peter Seiderer wrote:
> > I don't think it really fixes bug 10391. Bug 10391 is bogus by itself.
> > The update to 96344ff7125182989f98d3be8d111952a8f74e15 doesn't fix
> > anything, it only adds support for RPi Zero W.
>
> Saving a download as wiringpi-2.44.tar.gz containing something
> identifying itself as 2.42? I would call it a bug (not on the buildroot
> side but in the original git repository).
The release identified as 2.42 is in fact 2.44, since both tags point
to exactly the same commit.
> The suggested patch fixes the original complain of Bug 10391:
> 'WiringPi retrieves wrong (old) version'
>
> Any suggestion on how to reference the bug report otherwise?
I'll try to find a reasonable wording when applying, no need to respin.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-10-11 21:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 13:15 [Buildroot] [PATCH v1] wiringpi: bump version to 96344ff7125182989f98d3be8d111952a8f74e15 (the real 2.44) Peter Seiderer
2017-10-11 13:59 ` Thomas Petazzoni
2017-10-11 20:21 ` Peter Seiderer
2017-10-11 21:22 ` Thomas Petazzoni [this message]
2017-10-11 21:44 ` Thomas Petazzoni
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=20171011232259.16581f9a@windsurf.lan \
--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 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.