Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Yuri Bushmelev <jay4mail@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: why is zaurus-utils "gnu.tar.gz" in OE dev repo?
Date: Sun, 17 Jan 2010 13:39:57 +0300	[thread overview]
Message-ID: <201001171339.57694.jay4mail@gmail.com> (raw)
In-Reply-To: <alpine.LFD.2.00.1001170430200.4163@localhost>

Hello!
> $ git log recipes/zaurus-utils/files/gnu-tar.gz
> commit 5a7e0f0eb265c98248ffd23d4801d1e0c1af031b
> Author: Andrea Adami <andrea.adami@gmail.com>
> Date:   Wed Aug 12 00:09:31 2009 +0200
> 
>     zaurus-utils: create a common container for the various Zaurus tools
> 
>  can that tarball not be moved somewhere and downloaded?
> 
> http://projects.linuxtogo.org/pipermail/openembedded-commits/2009-August/
> 030396.html

IMHO, we can host it on LTG zaurus project page 
(zaurus.projects.linuxtogo.org) right after DNS will be fixed (ping to 
florian again) :)

-- 
Yuri Bushmelev



      reply	other threads:[~2010-01-17 10:43 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17  9:33 why is zaurus-utils "gnu.tar.gz" in OE dev repo? Robert P. J. Day
2010-01-17 10:39 ` Yuri Bushmelev [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=201001171339.57694.jay4mail@gmail.com \
    --to=jay4mail@gmail.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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