From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 0/4] Move download links away from Google Code
Date: Thu, 25 Feb 2016 22:41:14 +0100 [thread overview]
Message-ID: <20160225224114.2e07acb8@free-electrons.com> (raw)
In-Reply-To: <1456143807-3350-1-git-send-email-casantos@datacom.ind.br>
Dear Carlos Santos,
On Mon, 22 Feb 2016 09:23:23 -0300, Carlos Santos wrote:
> Alan Ott (3):
> dsp-tools: Move download link away from Google Code
> gst-dsp: Move download link away from Google Code
> gst-omapfb: Move download link away from Google Code
I've applied those three to the next branch. If you have some time,
adding a hash file for those packages would be good.
I haven't had the time to review the gtest/gmock patch for the moment,
which is why it has not been applied yet.
Thanks,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-02-25 21:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <444859483-2268-1-git-send-email-alan@softiron.co.uk>
2016-02-22 12:23 ` [Buildroot] [PATCH v2 0/4] Move download links away from Google Code Carlos Santos
2016-02-22 12:23 ` [Buildroot] [PATCH v2 1/4] dsp-tools: Move download link " Carlos Santos
2016-02-22 12:23 ` [Buildroot] [PATCH v2 2/4] gst-dsp: " Carlos Santos
2016-02-22 12:23 ` [Buildroot] [PATCH v2 3/4] gst-omapfb: " Carlos Santos
2016-02-22 12:23 ` [Buildroot] [PATCH v2 4/4] gtest, gmock: " Carlos Santos
2016-07-01 9:49 ` Yann E. MORIN
2016-07-01 10:43 ` Carlos Santos
2016-07-01 15:19 ` Yann E. MORIN
2016-02-25 21:41 ` Thomas Petazzoni [this message]
2016-02-26 11:43 ` [Buildroot] [PATCH v2 0/4] Move download links " Carlos Santos
2016-02-27 14:42 ` Thomas Petazzoni
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=20160225224114.2e07acb8@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