[1] I can give more details about this if asked, but among the things that this VCS makes easy are:
- different storages : use a DB instead of the standard filesystem hierarchy if you prefer (e.g., if you're using it to power a wiki-type website)
- different diff "units" : diffing can happen at the line level, or at, say, some other syntactic level (such as function body). Thus, when merge conflicts occurs can be finely tuned. Merge conflicts should be the VCS's way of saying "you should probably take a look at this before we continue"; if one user changes one part of a function (or method, or maybe even class), and another another part, it would be best if the merging user was made aware of the other change to avoid unexpected behavior. In fact, this idea can be brought to the point that merge-conflicts can be used sort of like locks or STM. Also, stuff like ydiff, which got I only heard about through HN
today, should be fairly easy to integrate
- different diffs : choose your own equality
- permissions and other settings by branch, type-enforced.
&c
On Sun, May 26, 2013 at 7:08 PM, Ivan Jovanovic <
ivan.jovanovic@gmail.com> wrote:
> Hi Emanuel,
>
> I have recently found here (
http://www.seas.upenn.edu/~cis194/final.html)
> some projects where authors were keen to help students to join an open
> source project.
> Might help.
>
> Cheers,
> Ivan
>
>
> _______________________________________________
> Beginners mailing list
>
Beginners@haskell.org
>
http://www.haskell.org/mailman/listinfo/beginners>