VCS Interface classes

[Randy Kramer]

On Monday 30 April 2007 03:26 pm, Andreas Pakulat wrote:
> On 30.04.07 14:39:20, Randy Kramer wrote:
> > Thus I can play around with the code locally but be able to revert changes 
as 
> > needed.  Then, when (if) I get to the point of actually making what I 
think 
> > might be a useful improvement to the project, I'll submit my changes to 
the 
> > remote repository.
> > 
> > I don't know whether repositoryRevision() vs. localRevision() is relevant 
to 
> > this, but even if not, my question would be: will the KDE VCS interface 
> > support such a mode of working?

Thanks for the reply!

> For stuff like that you need a distributed versioning system, for
> example svk or git. 

I should have mentioned I'm aware of that, but for projects that are currently 
not using svk or git, I plan to do the same kind of thing--the remote 
repository may be cvs or svn, but my local repository will probably be 
something else (but, it's the same concept if I keep a local svn or cvs 
repository).

Randy Kramer

> And we do have a interface for that, which currently 
> only has push/pull to sync with the remote repository. We need to refine
> that, but I think Matt is mostly the only person here with some
> experience.
> 
> Also note: This is not about the KDE VCS interface that Vic Fryzel is
> planning to work out, these interfaces are solely for the KDevelop
> platform.