You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@subversion.apache.org by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp> on 2005/02/13 08:29:47 UTC
[Issue 2210][RFC] How about /branches/svn-ruby?
Hi,
I propose /branches/svn-ruby or something so that kou can use it.
I think this may be a bold proposal, but makes developing and logging
transparent, and also makes reviewing smooth.
Because I'm interested in it, I am reviewing it bit by bit.
However, bindings are developed daily, patches getting larger and larger,
and logs changing day by day.
Also, I am not a full committer and do not have a privilege to approve
committing it even if I finish reviewing :-)
So, if it is not appropriate for kou to use /trunk,
how about creating /branches/svn-ruby or something and giving kou a commit
access to it until diffs of /trunk and the branch are completely reviewed
by someone?
If kou can use /branches/svn-ruby, everyone can know developing status and
its log, and review it.
Also, he can merge parts of binding codes to /trunk, if approved.
How do you like this idea?
P.S.
I am waiting for Ruby SWIG-based bindings being imported into the official
repository, and testing it with my environment.
The last test used followings and succeeded with no errors:
* Subversion trunk tree r12937 + svn-add-ruby-20050208.diff from
http://pub.cozmixng.org/~kou/diff/
(patch log: http://pub.cozmixng.org/~kou/diff/svn-add-ruby-20050208.log )
* Ruby 1.8.2 (2004-12-24) [i686-linux]
Logs:
nori1[15:47]% make check-swig-rb saba:~/svnwc/subversion-ruby
cd /home/nori1/svnwc/subversion-ruby/subversion/bindings/swig/ruby; /home/nori1/bin/ruby test/run-test.rb
Loaded suite test
Started
.........................
Finished in 53.504804 seconds.
25 tests, 142 assertions, 0 failures, 0 errors
Thanks,
--
|: Noritada KOBAYASHI
|: Dept. of General Systems Studies,
|: Graduate School of Arts and Sciences, Univ. of Tokyo
|: E-mail: nori1@dolphin.c.u-tokyo.ac.jp (preferable)
|: nori@esa.c.u-tokyo.ac.jp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by Kouhei Sutou <ko...@cozmixng.org>.
Hi,
In <20...@dolphin.c.u-tokyo.ac.jp>
"[Issue 2210][RFC] How about /branches/svn-ruby?" on Sun, 13 Feb 2005 17:29:47 +0900 (JST),
Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp> wrote:
> I propose /branches/svn-ruby or something so that kou can use it.
> I think this may be a bold proposal, but makes developing and logging
> transparent, and also makes reviewing smooth.
Great!
If this is actualized I'm so happy!
I hope many people agree with this suggestion.
--
kou
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by kf...@collab.net.
Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp> writes:
> Thank you for your answer, Garrett, Erik, and Max.
> So..., who has a privilege to add kou as a partial committer?
> Although I made a proposal, unfortunately I do not have a right to put
> it into practice.
> I must ask someone to be so kind as to do it.
You already have commit access, for the Japanese .po translation. So,
you can just go ahead and start work on the ruby branch.
See also r13007 :-).
-Karl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by Kobayashi Noritada <no...@dolphin.c.u-tokyo.ac.jp>.
Hi,
> >> +1, getting this into a branch would reduce the effort required for
> >> people to test it out, which would make it easier to review, etc.
> >
> > Same sentiment here. +1.
>
> Likewise, +1.
Thank you for your answer, Garrett, Erik, and Max.
So..., who has a privilege to add kou as a partial committer?
Although I made a proposal, unfortunately I do not have a right to put
it into practice.
I must ask someone to be so kind as to do it.
Regards,
--
|: Noritada KOBAYASHI
|: Dept. of General Systems Studies,
|: Graduate School of Arts and Sciences, Univ. of Tokyo
|: E-mail: nori1@dolphin.c.u-tokyo.ac.jp (preferable)
|: nori@esa.c.u-tokyo.ac.jp
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by Max Bowsher <ma...@ukf.net>.
Erik Huelsmann wrote:
>>> How do you like this idea?
>>
>> +1, getting this into a branch would reduce the effort required for
>> people to test it out, which would make it easier to review, etc.
>
> Same sentiment here. +1.
Likewise, +1.
Max.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by Erik Huelsmann <e....@gmx.net>.
> > How do you like this idea?
>
> +1, getting this into a branch would reduce the effort required for
> people to test it out, which would make it easier to review, etc.
Same sentiment here. +1.
bye,
Erik.
--
DSL Komplett von GMX +++ Superg�nstig und stressfrei einsteigen!
AKTION "Kein Einrichtungspreis" nutzen: http://www.gmx.net/de/go/dsl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Re: [Issue 2210][RFC] How about /branches/svn-ruby?
Posted by Garrett Rooney <ro...@electricjellyfish.net>.
Kobayashi Noritada wrote:
> Hi,
>
> I propose /branches/svn-ruby or something so that kou can use it.
> I think this may be a bold proposal, but makes developing and logging
> transparent, and also makes reviewing smooth.
>
> Because I'm interested in it, I am reviewing it bit by bit.
> However, bindings are developed daily, patches getting larger and larger,
> and logs changing day by day.
> Also, I am not a full committer and do not have a privilege to approve
> committing it even if I finish reviewing :-)
> So, if it is not appropriate for kou to use /trunk,
> how about creating /branches/svn-ruby or something and giving kou a commit
> access to it until diffs of /trunk and the branch are completely reviewed
> by someone?
> If kou can use /branches/svn-ruby, everyone can know developing status and
> its log, and review it.
> Also, he can merge parts of binding codes to /trunk, if approved.
>
> How do you like this idea?
+1, getting this into a branch would reduce the effort required for
people to test it out, which would make it easier to review, etc.
-garrett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org