<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
2011-12-01 16:37, Koen Kooi skrev:
<blockquote
cite="mid:878817F5-05C7-4749-BA0A-7ED04EE884BB@dominion.thruhere.net"
type="cite">
<pre wrap="">
Op 1 dec. 2011, om 14:16 heeft Philip Balister het volgende geschreven:
</pre>
<blockquote type="cite">
<pre wrap="">On 11/29/2011 03:06 PM, Koen Kooi wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
Op 29 nov. 2011, om 20:36 heeft Ulf Samuelsson het volgende geschreven:
</pre>
<blockquote type="cite">
<pre wrap="">On 2011-11-29 16:03, Richard Purdie wrote:
</pre>
<blockquote type="cite">
<pre wrap="">
</pre>
<blockquote type="cite">
<pre wrap="">2. <a class="moz-txt-link-rfc2396E" href="ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz">"ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz"</a> 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.
</pre>
</blockquote>
<pre wrap="">This is something to raise with the meta-oe maintainers. I think there
isn't a problem in OECore.
</pre>
</blockquote>
<pre wrap="">
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 = <a class="moz-txt-link-abbreviated" href="mailto:openembedded-core@lists.openembedded.org">openembedded-core@lists.openembedded.org</a>
or
meta-angstrom/.git/config
[sendemail]
to = <a class="moz-txt-link-abbreviated" href="mailto:angstrom-distro-devel@linuxtogo.org">angstrom-distro-devel@linuxtogo.org</a>
[format]
subjectprefix = "[meta-angstrom]"
No need to look in the README file with this.
</pre>
</blockquote>
<pre wrap="">
That assumes git-send-email is the preferred way, which it isn;'t for a lot of layers
</pre>
</blockquote>
<pre wrap="">
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.
</pre>
</blockquote>
<pre wrap="">
You can't fix stupid, sadly.
</pre>
</blockquote>
<br>
Tend to disagree.<br>
The whole purpose of OE is to make it possible for people,<br>
stupid or not, to go off and make things which they would<br>
not be able to do on their own.<br>
<br>
As I see it, it is no real drawback of adding this, and at least
some benefit.<br>
<br>
As for not beeing the preferred way, I think that people that engage
themselves<br>
in a layer should adopt the preferred way.<br>
<br>
Anyone seeing a bad layer, applicable only to a small subset of
users,<br>
interfering with their build should not be expected<br>
to put a lof of effort into the fix, except reporting it.<br>
Then the mailing list is probably the easiest thing to use.<br>
<br>
If this is not there, expect them to send it to the official list.<br>
BR<br>
Ulf<br>
<br>
<br>
<blockquote
cite="mid:878817F5-05C7-4749-BA0A-7ED04EE884BB@dominion.thruhere.net"
type="cite">
<pre wrap="">
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Openembedded-core mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Openembedded-core@lists.openembedded.org">Openembedded-core@lists.openembedded.org</a>
<a class="moz-txt-link-freetext" href="http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core">http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core</a>
</pre>
</blockquote>
<br>
<br>
<br>
<pre class="moz-signature" cols="72">--
Best Regards
Ulf Samuelsson
eMagii
</pre>
</body>
</html>