Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Ott <alan@softiron.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/5] Move download links away from Google Code
Date: Wed, 14 Oct 2015 18:02:54 -0400	[thread overview]
Message-ID: <561ED10E.5070405@softiron.co.uk> (raw)
In-Reply-To: <20151014235606.095399a1@free-electrons.com>

On 10/14/2015 05:56 PM, Thomas Petazzoni wrote:
> On Wed, 14 Oct 2015 17:51:18 -0400, Alan Ott wrote:
>
>> Alan Ott (5):
>>    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
> These three look good, but can you also add the hash files while you're
> at it?

Yes, will add.

Alan.

      reply	other threads:[~2015-10-14 22:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 21:51 [Buildroot] [PATCH 0/5] Move download links away from Google Code Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 1/5] dsp-tools: Move download link " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 2/5] gst-dsp: " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 3/5] gst-omapfb: " Alan Ott
2015-10-14 21:51 ` [Buildroot] [PATCH 4/5] gtest: Upgrade to GitHub HEAD Alan Ott
2015-10-14 21:55   ` Thomas Petazzoni
2015-10-14 22:00     ` Alan Ott
2015-10-15  7:10       ` Thomas Petazzoni
2015-10-19 19:29       ` Carlos Santos
2016-02-17 18:17         ` Carlos Santos
2016-02-17 20:50           ` Thomas Petazzoni
2016-02-18  0:13             ` Alan Ott
2016-02-18 16:14               ` Carlos Santos
2016-02-18 16:18                 ` Thomas Petazzoni
2016-02-18 19:26                   ` Carlos Santos
2015-10-14 21:51 ` [Buildroot] [PATCH 5/5] gmock: " Alan Ott
2015-10-14 21:56 ` [Buildroot] [PATCH 0/5] Move download links away from Google Code Thomas Petazzoni
2015-10-14 22:02   ` Alan Ott [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=561ED10E.5070405@softiron.co.uk \
    --to=alan@softiron.co.uk \
    --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