Re: svn commit: r15177 - trunk/subversion/bindings/swig/ruby/svn

On 2005-06-28 23:33+0900, Kouhei Sutou wrote:
> "Max Bowsher" <maxb@ukf.net> wrote:
> > Also, If this is just a temporary change for debugging, why commit it at
> > all?
>
> My answer is same as David's one.
>
> I'm debugging the problem that Ruby bindings courses
> segmentation fault on Jani's environment. But the problem
> doesn't occurred on my environment.

Here is a list what might be special in my system:

- apr and apr-util has been compiled with memory debugging enabled:
  "--enable-pool-debug=yes"
- I have hardware noexec stack in use
- The system is 64bit

> So I'm embedding debug
> print statements and checking svn-breakage list.
>
> I can ask Jani to apply my patches but that costs Jani. So I
> decided that I committed some debug print statements. Now,
> Ruby bindings tests on Jani's environment are automatically
> executed with some debug print statements.
>
> But I don't know which is better way to do this. Should I
> ask Jani to apply my patches or commit to trunk?

There are few options:

1) Use trunk

   pros: I don't have to do anything, it is easy for you
   cons: Trunk will be littered with debug statements, currently ruby
   bindings testing won't work on trunk (only get_diff is tested)

2) Use special branch for testing

   pros: I don't have to do anything (after initial setup), trunk will
         stay clean
   cons: it is semi easy for you (you have to sync with trunk)

3) Send patches to me

   pros: No disturbance in svn tree at all
   cons: Most laborious for you and me, we/I can screw up something with
   patches so I am not testing what you expect me to test

I favor 1 or 2, the initial setup for option 2 is fairly easy one, and
I could easily set the system a way that for this special purpose
branch only ruby bindings will be tested.

Kou and the rest of the team, please let me know what you like to do.

BR, Jani

-- 
Jani Averbach
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org