Thanks.
Id be interested to know what "best practoice" is violated by giving
each projectits own repository. In our case, where each project is
unique and has a unique list of qualified users, it seemd not only the
simpelst but also the most obvious way to organize our SVN server.
On 8/7/05, Mark Phippard <MarkP@softlanding.com> wrote:
> Jeffrey Kesselman <jeffpk@gmail.com> wrote on 08/07/2005 04:10:51 PM:
>
> > Can this be changed?
> >
> > This is not a requirement of subversion itself, it seems silly (and in
> > my case frustrating) to arbitrarily limit it in your interface.
>
> I assume there are no technical reasons it cannot be done. The feature
> was all written and established before I got here. Anyway, I entered
> issue 366 for this.
>
> http://subclipse.tigris.org/issues/show_bug.cgi?id=366
>
> FYI, I doubt that it was just an arbitrary decision. It will likely take
> special UI handling to make this work. I do not believe that anyone
> specifically set out to not allow this feature it just does not fall out
> naturally from the existing UI. It also goes against all best practices
> so a lot of people have not asked for it. Although I do recall others
> have mentioned it in the past.
>
> Mark
>
> _____________________________________________________________________________
> Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
> _____________________________________________________________________________
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Mon Aug 8 15:33:39 2005