Hi Hendrik, On Wed, May 25, 2011 at 12:33 PM, Hendrik Sattler <p...@hendrik-sattler.de> wrote: > Zitat von Luiz Augusto von Dentz <luiz.de...@gmail.com>: > [...] > > Both of those are already fixed in my releasing-2.0 tree, see > https://gitorious.org/openobex/mainline/commit/a862b3d3eec7c0008ebcfcf8a75150f8a3f3bc19 > > I already posted them here. Except one mail from Johan, nothing happened. I > admit that you did clean up ircp better than I did, though :) > Do you want to rebase the second patch on my tree, basically on-top of > https://gitorious.org/openobex/mainline/commits/ebc1dc31734bec3a2d8b172cf959b3844a29a3d9
Well in that case why you don't rebase your tree, my patches seems to fix just the issues with GCC 4.6 while yours fixes some other things so it might be clearer to just have them split meaning that you should rework your patches anyway. I know this sound inconvenient because you have posted similar changes before, but they are not upstream, besides that if I do rebase we will have a commit to fix another commit not upstream (e.g. handling scanf return correctly), which IMO is not good for sake of repository history. This fixes should go in as soon as possible. > Note that those are build warnings, not build errors (except when using > maintainer mode). Which is the whole point to force fixing and not just ignore them. -- Luiz Augusto von Dentz Computer Engineer ------------------------------------------------------------------------------ vRanger cuts backup time in half-while increasing security. With the market-leading solution for virtual backup and recovery, you get blazing-fast, flexible, and affordable data protection. Download your free trial now. http://p.sf.net/sfu/quest-d2dcopy1 _______________________________________________ Openobex-users mailing list Openobex-users@lists.sourceforge.net http://lists.sourceforge.net/lists/listinfo/openobex-users
