Patch for preliminary Mercurial integration in kdevplatform

[Gabor Garami]

And wat a problem? KUrl can point to local URIs too (like file:///) so
i don't think this idea no makes sense.
I thinking on a git KIO support - when I will grow up and be free :-)
- like svn (git+file:///, git+http://, git+ssh://).
It can make sense in kdevelop VCS url handling too, and VCS plugins
can translate easily between these protos and the proto used by
external tools.

Garami Gábor
hrgyster at gmail.com



On Wed, Mar 11, 2009 at 1:41 PM, Andreas Pakulat <apaku at gmx.de> wrote:
>> And how does KUrl doesn't fit the bill for remote repositories
>> locations as well for local-ones? Like git://user:password@server/path,
>> svn://server/trunk/stuff/
>
> Because not all VCS systems use urls to access remote repositories. CVS
> doesn't and I'm told that perforce doesn't do this either.
>
> Note the interfaces are supposed to be usable by other plugins and (at some
> point in the future) also by scripts that drive KDevelop.
>
> Andreas
>
> --
> You're growing out of some of your problems, but there are others that
> you're growing into.
>
> _______________________________________________
> KDevelop-devel mailing list
> KDevelop-devel at kdevelop.org
> https://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel
>