Hi Khem,
I've noticed that the gcc-4.8.0 patches have made it's way to
the master branch, but notice that you don't use the prefix patch numbers for
any newly generated patches.
http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta/recipes-devtools/gcc/gcc-4.8
e.g. 0036-gcc-4.8-PR56797.patch, as opposed to gcc-4.8-PR56797.patch
It makes it quicker to know the linear sequence from looking at the patches in
the gcc-4.8 folder, as well as the gcc-4.8.inc file, as time goes by.
This is what I had hoped to fix, when I submitted the refactored patches, since
it will help easily add/remove/port patches for current and future versions of
the gcc recipes. It is also useful, while attempting to compare patches across
multiple gcc recipes.
Best regards,
Elvis Dowson
_______________________________________________
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
