Re: [Valgrind-developers] gdb stub support

[Philippe W. <phi...@sk...>]

>> However, for this:
>>   * I suppose some papers have to be signed (?)
>>   * I suppose some patch files have to be then prepared
>>   * and someone with write access has to put it in the repository (in a
>> branch I guess)
>
> All this is news to me.

I once contributed some code to GNU emacs, and the procedure was more or 
less
the above.

For valgrind, the procedure(s) to follow to contribute some code is not 
clear to me:
There was a post asking some info about this
(http://sourceforge.net/mailarchive/message.php?msg_name=20080315052921.23DA11C7491%40localhost)
but I saw no feedback.

I know that copyright for VEX changes have to be assigned, but that is the 
only info I saw.
In the doc, there is a "readme developpers" but it only speaks about how to 
develop and test,
not about how to give code.

If there exists a "how to contribute code to valgrind", it would help 
beginners/small contributors
to provide some small changes and/or fix some small bugs

(e.g. I am sure I would be able to fix a part of 
http://bugs.kde.org/show_bug.cgi?id=157154 myself but
currently how to change "4" in "12" is mysterious to me  :)

Philippe