LOL Well... the problem is that an "svn mv" from /incubator/subversion/ to /subversion/ introduces an artificial breakage in the history. It is actually quite disruptive for tracking history (which is very important to us).
(and yes, because of that history issue, I personally have no problem putting podlings at the top-level in our repository; it *is* version control, and we can always remove failed podlings' code from anywhere) Cheers, -g On Tue, Nov 10, 2009 at 14:38, Davanum Srinivas <dava...@gmail.com> wrote: > Personally i am ok with #1, but i am not sure if "svn switch --relocate" too > much of a burden for you guys :) > > On 11/10/2009 02:27 PM, Greg Stein wrote: >> >> There are two other issues to discuss for the Subversion podling: >> >> * moving the mailing lists directly to @subversion.apache.org >> * placing the source code at /subversion/ rather than >> /incubator/subversion/ >> >> We are hoping to minimize overall disruption to the community with a >> move to incubator space, then a move to apache space. >> >> Cheers, >> -g >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org >> For additional commands, e-mail: general-h...@incubator.apache.org >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
