From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] lksctp-tools: new package
Date: Wed, 2 Mar 2016 18:37:57 -0300 [thread overview]
Message-ID: <56D75D35.5050201@zacarias.com.ar> (raw)
In-Reply-To: <20160302222600.618f2a64@free-electrons.com>
On 02/03/16 18:26, Thomas Petazzoni wrote:
> We already have a submission for the same package from Yegor
> (initially submitted on Feb 26), which Arnout reviewed, and Yegor
> posted a v2 on Feb 29.
>
> Best regards,
>
> Thomas
Gah missed it, interval between "need it" and "submit it" was short enough.
Still, would be good to spin a v3 with the source code purge otherwise a
bunch of .c files end in the target.
Regards.
next prev parent reply other threads:[~2016-03-02 21:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 21:07 [Buildroot] [PATCH] lksctp-tools: new package Gustavo Zacarias
2016-03-02 21:26 ` Thomas Petazzoni
2016-03-02 21:37 ` Gustavo Zacarias [this message]
2016-03-02 21:39 ` Thomas Petazzoni
2016-03-02 21:50 ` Yegor Yefremov
2016-03-02 21:56 ` Gustavo Zacarias
2016-03-02 22:16 ` Yegor Yefremov
2016-03-02 22:22 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2016-02-26 9:24 yegorslists at googlemail.com
2016-02-26 21:40 ` Arnout Vandecappelle
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=56D75D35.5050201@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.