From: Takehiro T. <tak...@in...> - 2002-08-25 10:36:35
|
>>>>> "A" == Alexander Leidinger <Alexander@Leidinger.net> writes: A> Post a patch to lame-dev, wait a week so interested people can A> look at it (Mark way want to be prepared for the testcase A> change), then commit it if nobody complains. If someone finds a A> bug after the commit, get enough info to fix it, if nobody A> cares enough to provide you with enough infos but reverts to a A> known good version instead (without your OK), I will speak A> up. Reverting without providing enough infos to reproduce the A> bug is bad. Ok, I will back to the way in the old days; Mail the patch, wait a week, commit it. But there are quite large problem. I have to divide the whole patcheds into some pieces, if we want to merge my branch into the head branch step by step. To divide the patch is quite hard work and causes some nasty bugs. >> Subject: Re: [Lame-dev] reverting back to last known working CVS >> From: Robert Hegemann <Rob...@gm...> >> He said my test is not enough. But, I can't reproduce the >> "BUG" what he said still. A> Is the problem by any chance related to compiler A> options/version/type (I don't have the message at hand)? It seems not. His and my compiler is almost same (gcc 3.0.x), and environments are same (Linux 2.4.x kernel system). He told me that I have to check the code with more lengthy songs. so I tested with some, but I could not reproduce. A> Was Robert the only one seeing the problem? Do both of you A> ruled out differences in the development environment? Did you A> asked him to test if you actual version does the same? Ok, I will mail the exact patch and test method, in the other mail. >> "why you mail me directly ? why don't you mail it to and >> discuss it on lame-dev mailing list ?" A> Because I thought the question isn't "Does the branch get merged?" Ok, I understood. No problem. -- Takehiro TOMINAGA // may the source be with you! |