[OE-core] [PATCH] webkitgtk: add a new recipe for latest upstream version

[Burton, Ross]

On 11 September 2015 at 08:12, <alexander.kanavin at linux.intel.com> wrote:

> Wait a moment, why do we need a second signed-off-by there? The commit
> that adds the custom patch already has my signed-off-by, so it is
> redundant to repeat it I think.
>

Because the patch and the commit are not always tied together - if the
patch gets copied for another recipe then there's no way to find out who
added it, and VCS migrations complicate chasing history.  It's not uncommon
to be chasing down who created a patch to get additional context some seven
years after it was created, which at this point in time means traversing
two repos and three VCS migrations.   I know this happens because I've
spent 30 minutes chasing a crazy patch back to monotone commits in
oe-classic only to find that I created it back in 2008...

Another real example: python3 has some setuptool patches which were added
by Khem.  From the Signed-off we can see that the patch was actually
created by Richard and simply copied from the python2 recipes.

Ross
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20150911/bf88a7d1/attachment-0002.html>