Patch for preliminary Mercurial integration in kdevplatform

[Evgeniy Ivanov]

On Thu March 19 2009 01:01:19 Fabian Wiesel wrote:

> Ultimately, I'd prefer to go in the direction of a more object oriented
> approach, too. Maybe you remember my remark on why a repository is not
> an object? At first, I thought it was straight forward text-book case
> (Every noun a class: A working-directory/repository has versioned
> objects (files and directories...). But after giving it some more
> thought, I am not so sure about it anymore. The problem is, there is
> already the project tree. And replicating almost the same directory
> structure in the repository (or worse, when there are more VCSs:
> repositories) seems somewhat bad design. On the other hand, the
> relationship between repositories and directory trees can become quite
> complex: A project tree may correspond to a
> child-directory in a repository, or the root of the repository may
> correspond to some subdirectory in the project-tree. One sub-tree may
> be also under control of another VCS, one part of the sub-tree is under
> control of another VCS, but not the current one (svn:external).
> Just food for thought :).
>


We had an idea to port some API from QGit (it's really a very very very good 
application with a lot of API work done). But unfortunately last summer was 
hard for me (family problems made few breaks and took much time and my 
"force"), so we chosen easier way.
API in QGit is very cool (and UI is definitely the best among other git uis).

-- 
Best regards, Evgeniy.
Key Fingerprint: F316B5A1F6D2054FCD18B74A95400ABB1FE567A3

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kdevelop-devel/attachments/20090320/e011f8f8/attachment.sig>