|
From: Xiao, W. W <wei...@in...> - 2016-05-09 07:02:49
|
I have fixed Valgrind two unsupported x86_32 instructions: popcount and sysenter. how can I check in my bug fixings to Valgrind developing source code tree? (I mean they will be available to others in the next release) Thanks Wei Xiao |
|
From: Tom H. <to...@co...> - 2016-05-09 07:26:43
|
On 09/05/16 08:02, Xiao, Wei W wrote: > I have fixed Valgrind two unsupported x86_32 instructions: popcount and > sysenter. > > how can I check in my bug fixings to Valgrind developing source code > tree? (I mean they will be available to others in the next release) Open a bug and attach a patch, or attach the patch to an existing bug if there is one. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Xiao, W. W <wei...@in...> - 2016-05-09 07:36:38
|
So I need to open a bug in https://bugs.kde.org/enter_bug.cgi?product=valgrind, right? I want to contribute to Valgrind development and how can i make "svn ci" to its source code repository? Thanks Wei Xiao -----Original Message----- From: Tom Hughes [mailto:to...@co...] Sent: Monday, May 09, 2016 3:26 PM To: Xiao, Wei W; val...@li... Subject: Re: How can i contribute my bug fixings to Valgrind developing source code tree On 09/05/16 08:02, Xiao, Wei W wrote: > I have fixed Valgrind two unsupported x86_32 instructions: popcount > and sysenter. > > how can I check in my bug fixings to Valgrind developing source code > tree? (I mean they will be available to others in the next release) Open a bug and attach a patch, or attach the patch to an existing bug if there is one. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |
|
From: Tom H. <to...@co...> - 2016-05-09 07:40:07
|
On 09/05/16 08:36, Xiao, Wei W wrote: > So I need to open a bug in https://bugs.kde.org/enter_bug.cgi?product=valgrind, right? Correct. > I want to contribute to Valgrind development and how can i make "svn ci" to its source code repository? Well you can't, at least initially. Rather you will post patches and somebody that is already a committer will review and commit them. Eventually the project owners may decide to allow you to commit stuff yourself if you are doing a lot of work and the quality is good. That's how most open source projects work. Tom -- Tom Hughes (to...@co...) http://compton.nu/ |