[oe] [RFC] Enable --hash-style=both for all recent gcc4 targets

[Tom Talpey]

At 06:43 PM 10/15/2008, Holger Freyther wrote:
>Wow, I had to read that a couple of times. In Linux terms I would have to add  
>a S-O-B to the commit. If it goes through your hands you add your S-O-B as 
>well, if you just review and like the patch you ack?

If you write code and add it to a patch, you generally sign it (S-O-B)
because you're asserting that your addition adheres to the relevant
license(s). If you merely approve of code and don't add any, then you
ack it (A-B).

There are lots of other amusing lines that are often added, but the
S-O-B one is the key, since it establishes the chain of responsibility.
Beginning with the submitter!

Do OE recipes have any particular licensing to govern any S-O-B terms?
If that's documented somewhere, I'd be interested to see it. There isn't
a license in the tree, that I've found.

Tom.