From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 10391] WiringPi retrieves wrong (old) version
Date: Wed, 11 Oct 2017 11:29:52 +0000 [thread overview]
Message-ID: <bug-10391-163-BkFp4qVU70@https.bugs.busybox.net/> (raw)
In-Reply-To: <bug-10391-163@https.bugs.busybox.net/>
https://bugs.busybox.net/show_bug.cgi?id=10391
--- Comment #3 from srg.venema at gmail.com ---
Have a closer look at:
warning: Remote branch 2.44 not found in upstream origin, using HEAD instead
Could not fetch special ref '2.44'; assuming it is not special.
It goes ahead to download 2.42 instead.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2017-10-11 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-11 11:21 [Buildroot] [Bug 10391] New: WiringPi retrieves wrong (old) version bugzilla at busybox.net
2017-10-11 11:23 ` [Buildroot] [Bug 10391] " bugzilla at busybox.net
2017-10-11 11:28 ` bugzilla at busybox.net
2017-10-11 11:29 ` bugzilla at busybox.net [this message]
2017-10-11 13:06 ` bugzilla at busybox.net
2017-10-11 13:28 ` bugzilla at busybox.net
2017-10-11 14:23 ` bugzilla at busybox.net
2017-10-11 14:44 ` bugzilla at busybox.net
2017-10-31 20:59 ` bugzilla at busybox.net
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=bug-10391-163-BkFp4qVU70@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--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