Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: Feedback on building openembedded-core for qemuarm. Excerpts from buildlog
Date: Thu, 01 Dec 2011 08:16:04 -0500	[thread overview]
Message-ID: <4ED77E14.1080309@balister.org> (raw)
In-Reply-To: <7E3B66F1-28FC-45D4-BA89-193D9EA6DCA6@dominion.thruhere.net>

On 11/29/2011 03:06 PM, Koen Kooi wrote:
> 
> Op 29 nov. 2011, om 20:36 heeft Ulf Samuelsson het volgende geschreven:
> 
>> On 2011-11-29 16:03, Richard Purdie wrote:
>>>
>>>> 2.    "ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz" is no longer
>>>> available.
>>>>          tzdata , same problem.
>>>>          The recipe is located in two places.
>>>>          meta-openembedded/meta-oe/recipes-extended/tz*/tz*.bb have the
>>>> problem
>>>>          This is what the build uses.
>>> This is something to raise with the meta-oe maintainers. I think there
>>> isn't a problem in OECore.
>>
>> Since we now have a large number of layers, maybe it is a good
>> idea to define in each layer,  how the "git send email" should behave in
>> by providing a better ".git/config" file in the trunk?
>>
>>
>> I.E:
>>
>> [sendemail]
>>    to = openembedded-core@lists.openembedded.org
>>
>> or
>> meta-angstrom/.git/config
>> [sendemail]
>>    to = angstrom-distro-devel@linuxtogo.org
>> [format]
>>    subjectprefix = "[meta-angstrom]"
>>
>>
>> No need to look in the README file with this.
> 
> That assumes git-send-email is the preferred way, which it isn;'t for a lot of layers

Even if it is not the preferred way, it would direct the discussion to
the appropriate list. This would reduce the number of mis-directed
emails to this list.

And we know that no one reads the README's :)

Philip

> 
> 
> 
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core



  parent reply	other threads:[~2011-12-01 13:22 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-26 11:24 Feedback on building openembedded-core for qemuarm. Excerpts from buildlog Ulf Samuelsson
2011-11-26 12:38 ` Eric Bénard
2011-11-26 14:14   ` Ulf Samuelsson
2011-11-27 11:40   ` Richard Purdie
2011-11-27 11:47     ` Eric Bénard
2011-11-28 21:31       ` Ulf Samuelsson
2011-11-29  8:48     ` Eric Bénard
2011-11-29 15:03 ` Richard Purdie
2011-11-29 15:50   ` Koen Kooi
2011-11-29 16:03     ` Richard Purdie
2011-12-01  1:52       ` Khem Raj
2011-12-01  9:26         ` Richard Purdie
2011-11-29 19:36   ` Ulf Samuelsson
2011-11-29 20:06     ` Koen Kooi
2011-11-29 21:12       ` Ulf Samuelsson
2011-12-01 13:16       ` Philip Balister [this message]
2011-12-01 15:37         ` Koen Kooi
2011-12-01 16:31           ` Ulf Samuelsson
2011-12-02  9:46             ` Frans Meulenbroeks
2011-12-02  9:49             ` Koen Kooi
2011-12-02 22:36               ` Ulf Samuelsson
2011-11-29 21:18   ` Ulf Samuelsson
2011-11-30 17:30     ` Scott Garman
2011-12-01 14:49       ` Ulf Samuelsson
2011-12-03 20:03         ` Ulf Samuelsson
2011-12-04 11:20           ` Henning Heinold
2011-12-04 11:35             ` Richard Purdie
2011-12-07 22:51               ` Khem Raj
2011-12-07 23:45                 ` Ulf Samuelsson

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=4ED77E14.1080309@balister.org \
    --to=philip@balister.org \
    --cc=openembedded-core@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