From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncftp: fix host/target confusion
Date: Tue, 7 Mar 2017 21:10:02 +0100 [thread overview]
Message-ID: <20170307211002.26e35c3f@free-electrons.com> (raw)
In-Reply-To: <87tw75av93.fsf@dell.be.48ers.dk>
Hello,
On Tue, 07 Mar 2017 17:48:08 +0100, Peter Korsgaard wrote:
> >>>>> "Peter" == Peter Korsgaard <peter@korsgaard.com> writes:
>
> >>>>> "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.
>
> After sending them a detailed mail explaining the issue with them
> updating the tarballs and a diff of the changes, I got the following
> answer:
>
> > Is this update intentional? Why was the tarball regenerated?
>
> Yes.
>
> Which wasn't exactly helpful :/ I'll send a patch to update our hash,
> but I will NOT update the tarball on sources.buildroot.net yet.
Isn't sources.buildroot.net going to automatically pick up the new
tarball once you change the hash?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-03-07 20:10 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
2017-03-07 16:48 ` Peter Korsgaard
2017-03-07 20:10 ` Thomas Petazzoni [this message]
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=20170307211002.26e35c3f@free-electrons.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox