On Thu, Feb 10, 2011 at 07:02:18PM +0100, Fabian Richter wrote:
> Am Thu, 10 Feb 2011 11:24:09 -0600
> schrieb Ryan Schmidt <subversion-2011a_at_ryandesign.com>:
> > On Feb 10, 2011, at 09:59, Stefan Sperling wrote:
> >
> > >> and can you please add an --force switch to
> > >> still being able to create Repositories within the path of another?
> > >
> > > That's a reasonable request, I think. Not a usual use case but why
> > > not?
> >
> > Really? What possible reason could exist for doing this? :)
I have no idea, to be honest. But then again I'm not going to guess.
Maybe someone can present a good use case for this? Dunno.
> We are using Redmine as a projectmanagement Tool and there projects can
> have subprojects. This hierarchy we also want in the file system level
> so we can see from the url of the repos which category it belongs to.
I would recommend against doing this because it's usually not
done this way. If you do this you might run into various problems.
Especially if you're ever going to use backup scripts or other repository
management tools that exist -- they might fail in some way.
You should put your repositories into a flat hierarchy.
But that does not prevent you from naming them in accordance with
the hierarchy you see in redmine:
project1
project1-subproject1
project1-subproject2
project1-subproject2-subproject1
project2
... etc.
Basically, use dashes instead of slashes.
You can also put repositories for different top-level projects into
separate directories if a single flat hierarchy becomes too cumbersome:
project1-repositories/ <-- a normal directory
project1 <-- a repository
project1-subproject1 <-- a repository
project1-subproject2 <-- a repository
project1-subproject2-subproject1 <-- a repository
project2-repositories/ <-- a normal directory
project2 <-- a repository
... etc.
> @Stefan: I have no idea what the former Version was, but I upgraded
> from debian Lenny to squeeze so it was probably 1.5.1.
Then the behaviour isn't new. I thought you were implying that
what you were trying to do was working with an older version?
> Would it hurt to add a force switch? I mean its at the users risk isnt
> it?
Let's add it only if someone comes up with a good reason for having it.
Thanks,
Stefan
Received on 2011-02-10 22:03:15 CET