Hi,
El 06/05/10 10:05, Gour escribió:
[...]
Edward> My question wasn't intended to start a debate about the relative
Edward> merits of various source code control systems. Rather, I want
Edward> to know whether I should be concerned, (or very very concerned)
Edward> about the stability of bzr.
[...]
That's why I believe that Fossil is worthy to be tried since it is
written by the guy who wrote SQlite and it is very robust system.
It gives distributed VCS with autosync feature enabling to have sort
of central-repo from/to where everyone pulls/push, integrated wiki and
bugtracker...all of these is self-hosted on simple CGI-enabled server.
[...]
It seems like a worth try. The self contained approach of Fossil about
distributed version control system with integrated/distributed bug
tracking, wiki and blog in a minimalistic code base seems a nice
addition to Leo, now that some people, like Villie, are thinking in the
integration of documentation storage inside Leo and may be helps in the
way that people work collaboratively on source code in mixed
environments without using Leo (they can sync against fossil). Where I
live a lot of people doesn't have any preference about DVCS or
programming envs because they simply don't use them and also programming
is not an extended experience/knowledge, so putting things like
Leo/Fossil in the mindset of people doesn't fight with acquired (bad)
habits and innovation could be smother.
Cheers,
Offray
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to
[email protected].
For more options, visit this group at
http://groups.google.com/group/leo-editor?hl=en.
