Just want to say that this project may produce very usefull software. Have been serching for something like this before, but are to lazzy to do the work myself. Keep the good work up!
PS. Some nice java client would be fun, but should be low priority.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, it was the same for me.
I've been searching for a similar tool all over the net; the nearest piece of sw is wiki, but it's not planned for revision control...
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Yes, I already checked this project before starting phpVcs.
I don't like the patches system that wvs uses; basically they're thinking about a system where people submit patches, then the project admin will apply them. After a patch is applied, a new release is automatically generated.
In phpVcs architecture the patch concept does not exists; only two kind of object exists, inodes and versions. So every file release can be very different from the previous one; overall, each developer is indipendent and should not check other's patches before committing his version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Just want to say that this project may produce very usefull software. Have been serching for something like this before, but are to lazzy to do the work myself. Keep the good work up!
PS. Some nice java client would be fun, but should be low priority.
Thanks, it was the same for me.
I've been searching for a similar tool all over the net; the nearest piece of sw is wiki, but it's not planned for revision control...
I also found http://sourceforge.net/projects/wvs/ . It seems to be close, but the activity is low (I havn't tried it).
Yes, I already checked this project before starting phpVcs.
I don't like the patches system that wvs uses; basically they're thinking about a system where people submit patches, then the project admin will apply them. After a patch is applied, a new release is automatically generated.
In phpVcs architecture the patch concept does not exists; only two kind of object exists, inodes and versions. So every file release can be very different from the previous one; overall, each developer is indipendent and should not check other's patches before committing his version.