<br><br><div class="gmail_quote">2011/12/1 Ulf Samuelsson <span dir="ltr"><<a href="mailto:openembedded-core@emagii.com">openembedded-core@emagii.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div bgcolor="#FFFFFF" text="#000000">
2011-12-01 16:37, Koen Kooi skrev:
<div><div></div><div class="h5"><blockquote type="cite">
<pre>Op 1 dec. 2011, om 14:16 heeft Philip Balister het volgende geschreven:
</pre>
<blockquote type="cite">
<pre>On 11/29/2011 03:06 PM, Koen Kooi wrote:
</pre>
<blockquote type="cite">
<pre>Op 29 nov. 2011, om 20:36 heeft Ulf Samuelsson het volgende geschreven:
</pre>
<blockquote type="cite">
<pre>On 2011-11-29 16:03, Richard Purdie wrote:
</pre>
<blockquote type="cite">
<pre></pre>
<blockquote type="cite">
<pre>2. <a href="ftp://elsie.nci.nih.gov/pub/tzcode2011i.tar.gz" target="_blank">"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>This is something to raise with the meta-oe maintainers. I think there
isn't a problem in OECore.
</pre>
</blockquote>
<pre>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 href="mailto:openembedded-core@lists.openembedded.org" target="_blank">openembedded-core@lists.openembedded.org</a>
or
meta-angstrom/.git/config
[sendemail]
to = <a href="mailto:angstrom-distro-devel@linuxtogo.org" target="_blank">angstrom-distro-devel@linuxtogo.org</a>
[format]
subjectprefix = "[meta-angstrom]"
No need to look in the README file with this.
</pre>
</blockquote>
<pre>That assumes git-send-email is the preferred way, which it isn;'t for a lot of layers
</pre>
</blockquote>
<pre>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>You can't fix stupid, sadly.
</pre>
</blockquote>
<br></div></div>
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><font color="#888888">
Ulf</font><br></div></blockquote></div><br>My two cents:<br>If I see a small problem in a layer that I am not working on and submitting a patch is easy (e.g. committing the patch, doing a send-email) I would probably do so.<br>
If it becomes harder (since I have to find what list it needs to be send to) chances that the effort is made become smaller and actually depending on the time at hand<br>If i have to set up a git mirror just for this single patch, forget it.<br>
<br>I think if we want to encourage people fixing and submitting patches it helps to have a mailing address in the config file.<br>But of course if you prefer to do maintenance only with the happy few, this is less desirable (but then you should probably consider not accepting mailed patches at all)<br>
<br>frans<br>