All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rolf Leggewie <no2spam@nospam.arcornews.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: move marvell firmware tarballs out of OE repo?
Date: Sun, 17 Jan 2010 20:44:06 +0100	[thread overview]
Message-ID: <hivpa7$hib$3@ger.gmane.org> (raw)
In-Reply-To: <alpine.LFD.2.00.1001170412460.4070@localhost>

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?

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.




  reply	other threads:[~2010-01-17 19:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-17  9:15 move marvell firmware tarballs out of OE repo? Robert P. J. Day
2010-01-17 19:44 ` Rolf Leggewie [this message]
2010-01-17 21:46   ` Paul Menzel
2010-01-18  0:31     ` Rolf Leggewie
2010-01-18  8:21       ` Marcin Juszkiewicz
2010-01-18  8:27         ` Robert P. J. Day

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='hivpa7$hib$3@ger.gmane.org' \
    --to=no2spam@nospam.arcornews.de \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.