Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Sat, 27 Feb 2016 15:42:46 +0100	[thread overview]
Message-ID: <20160227154246.19bd94ea@free-electrons.com> (raw)
In-Reply-To: <977326203.1415529.1456486998729.JavaMail.zimbra@datacom.ind.br>

Carlos,

On Fri, 26 Feb 2016 08:43:18 -0300 (BRT), Carlos Santos wrote:

> > I've applied those three to the next branch. If you have some time,
> > adding a hash file for those packages would be good.
> 
> Done:
> 
>    http://patchwork.ozlabs.org/patch/588914/
>    http://patchwork.ozlabs.org/patch/588916/

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

      reply	other threads:[~2016-02-27 14:42 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   ` [Buildroot] [PATCH v2 0/4] Move download links " Thomas Petazzoni
2016-02-26 11:43     ` Carlos Santos
2016-02-27 14:42       ` 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=20160227154246.19bd94ea@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