From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncftp: fix host/target confusion
Date: Fri, 03 Mar 2017 23:08:17 +0100 [thread overview]
Message-ID: <87bmtif1ym.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <6166a3fa-e697-bae9-2dbf-e1153472a027@mind.be> (Arnout Vandecappelle's message of "Fri, 3 Mar 2017 23:04:03 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 03-03-17 21:50, Peter Korsgaard wrote:
>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>>
>> Hi,
>>
>> > I'm not sure what to do in this case? Blindly take the new upstream
>> > version? Complain to upstream?
>>
>> We should probably update. I have mailed support at ncftp.com asking them
>> what happened.
>>
>> I will let you know when/if I hear back from them.
> This is terribly annoying, however, since we just released 2017.02 with the
> 7abd3e8f hash. So now people are downloading it from sources.buildroot.net. But
> if we apply the new hash and update sources.buildroot.net, people using the
> 2017.02 release have no way to download ncftp anymore...
Indeed :/ We can naturally fix it in 2017.02.1, but still. Lets see what
the ncftp guys say.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2017-03-03 22:08 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 22:54 [Buildroot] [PATCH] ncftp: fix host/target confusion Thomas Petazzoni
2017-03-01 20:13 ` Yann E. MORIN
2017-03-01 20:48 ` Thomas Petazzoni
2017-03-02 16:28 ` Peter Korsgaard
2017-03-02 19:07 ` Danomi Manchego
2017-03-02 20:43 ` Thomas Petazzoni
2017-03-03 20:50 ` Peter Korsgaard
2017-03-03 22:04 ` Arnout Vandecappelle
2017-03-03 22:08 ` Peter Korsgaard [this message]
2017-03-07 16:48 ` Peter Korsgaard
2017-03-07 20:10 ` Thomas Petazzoni
2017-03-07 21:10 ` Peter Korsgaard
2017-04-14 22:35 ` Arnout Vandecappelle
2017-04-26 6:48 ` 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=87bmtif1ym.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.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