[oe] move marvell firmware tarballs out of OE repo?

[Paul Menzel]

Am Sonntag, den 17.01.2010, 20:44 +0100 schrieb Rolf Leggewie:
> Robert P. J. Day wrote:
> >   (this is the first in a small number of postings to clarify the
> > purpose of some tarballs in the OE dev repository
> 
> DUDE!
> 
> Why are you again wasting everybody's time?  I thought you wanted to use
> git log yourself to find out and then targeting the relevant people in a
> focused fashion instead of flooding the list with this junk?

(Very polite! ;-))

If you look at his other messages you will see that this was probably
not Robert’s intention and that he did his best.

> BTW, re your suggestion to add READMEs.  Well, I guess that is fine.
> But for people who aren't too lazy to use "git log --find-copies-harder"
> the answers are often right there.

(Again not a nice implication.)

Anyways looking at the relevant commit

        $ git log --follow recipes/firmwares/marvell-gspi-fw/9.70.3-p37.tar.gz
        commit 7ea3026aa3c216f9943711771e9245b2b6ff7c84
        Author: Marcin Juszkiewicz <marcin at buglabs.net>
        Date:   Thu Apr 23 14:01:35 2009 +0200
        
            marvel-gspi-fw: added firmware for WiFi bugmodule
            
            This is firmware for not-yet-released-into-sales wifi/bt bugmodule.

it does not explicitly say, why the firmware cannot be made public
somewhere or if it ever will be available.

Having “perfect” commit messages in OE seems to still be a current
topic, so having a README file is certainly an idea I support at least
for the files the commit messages can not be changed anymore. This would
definitely help me and lower the barrier/learning curve to get to know
OE.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Dies ist ein digital signierter Nachrichtenteil
URL: <http://lists.openembedded.org/pipermail/openembedded-devel/attachments/20100117/8df9821a/attachment-0002.sig>