[MonoDevelop] VersionControl Add-in for Perforce
Lluis Sanchez Gual
lluis at novell.com
Wed Jul 2 06:58:56 EDT 2008
El dc 02 de 07 de 2008 a les 11:16 +0200, en/na Federico Di Gregorio va
> Il giorno mar, 01/07/2008 alle 22.05 -0400, Michael Hutchinson ha scritto:
> > > - It doesn't look like there's any way for MonoDevelop to figure out
> > > that a particular solution/project/file/etc. is already under version
> > > control -- I only see hooks to "checkout" and "publish" code. If this
> > > doesn't exist, that would obviously be a neat feature.
> > It does do that. The real fun is all in the Repository instances that
> > the VersionControlSystem returns, which has (among many other things)
> > an IsVersioned (string localPath) method.
> I am working at bzr support (it just show the correct status right now)
> and I don't understand why so many repository instances and what
> sub-repositories are? Can someone shed some light on
> HasChildRepositories and GetChildRepositories()?
A repository is basically something you can check-out. Sub-repositories
allow organizing repositories in a hierarchy. This hierarchy is shown in
the check-out dialog when you register a new repository.
Fore example, with SVN you can check-out any directory, so given an SVN
url, the list of sub-repositories is the list of sub-directories in that
I don't know how bzr works. If every url corresponds to exclusively one
module you can checkout, then just make HasChildRepositories return
false. If given an url, bzr allows browsing through a list of modules
located in that url, then you would have a repository representing that
url, and one sub-repository for each module.
More information about the Monodevelop-list