From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Requesting libvte
Date: Tue, 16 Jan 2018 21:02:04 +0100 [thread overview]
Message-ID: <20180116210204.3773f989@windsurf> (raw)
In-Reply-To: <ZRit0bTMnKM_Wv_-OSp5Hg0NRDUP5SuRTtNFFfhnCqlnu5Jr24Y5Qp2AiqAy1J187ve2bK9WHz4e6l0mHgMZC5CvW-G8itWNrlVj4yNv4Ok=@protonmail.com>
Hello,
On Tue, 16 Jan 2018 14:20:45 -0500, Biz.122 wrote:
> Ok, as you correctly assumed I am a newb to open-source contributions - hence my unintended ignorant suggestion.
> I took a look at the list again, and it seems as if someone was unexpectedly quick on his feet:
> http://lists.busybox.net/pipermail/buildroot/2018-January/211713.html
>
> Should I attempt to make a patch for this or leave it to him?
Since Stefan has taken up the task, I believe what you could do to help
is test his patch, and report if it works for you (or not).
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2018-01-16 20:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-16 10:44 [Buildroot] Requesting libvte Biz.122
2018-01-16 14:11 ` Thomas Petazzoni
2018-01-16 19:20 ` Biz.122
2018-01-16 20:02 ` Thomas Petazzoni [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=20180116210204.3773f989@windsurf \
--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