From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lft: new package
Date: Fri, 13 May 2016 19:07:40 -0300 [thread overview]
Message-ID: <5736502C.7040402@zacarias.com.ar> (raw)
In-Reply-To: <20160513233427.43dbe4e1@free-electrons.com>
On 13/05/16 18:34, Thomas Petazzoni wrote:
> I guess the chance of seeing the patches merged upstream is pretty
> small, unfortunately :/ Have you talked with upstream about the silly
> form-based download method?
>
> Thanks!
>
> Thomas
Hi.
It seems unlikely, i've emailed them about the build patches and never
got any reply back which i was hoping for to ask about the form.
Regards.
prev parent reply other threads:[~2016-05-13 22:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-03 18:30 [Buildroot] [PATCH] lft: new package Gustavo Zacarias
2016-05-13 21:34 ` Thomas Petazzoni
2016-05-13 22:07 ` Gustavo Zacarias [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=5736502C.7040402@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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.