From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] ncftp: fix host/target confusion
Date: Wed, 26 Apr 2017 08:48:39 +0200 [thread overview]
Message-ID: <87mvb3r7eg.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1ce8fc39-f994-0e53-4cbe-05a89a4c481f@mind.be> (Arnout Vandecappelle's message of "Sat, 15 Apr 2017 00:35:29 +0200")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
> On 07-03-17 22:10, Peter Korsgaard wrote:
>>>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
>>
>>
>> >> > 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?
>>
>> Hmm, I guess so. It just runs 'make -k source'. I guess we should wait
>> until we are ready to release 2017.02.1 then.
> So this issue missed 2017.02.1 :-)
Argh, yes :/
> However, we can do a workaround: in master, we can use the tar.gz file instead
> of the tar.xz. That way, there can be two separate tarballs on
> sources.buildroot.net for the two versions.
Ahh yes, good idea - I'll send a patch doing that.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-04-26 6:48 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
2017-03-07 21:10 ` Peter Korsgaard
2017-04-14 22:35 ` Arnout Vandecappelle
2017-04-26 6:48 ` Peter Korsgaard [this message]
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=87mvb3r7eg.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 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.