4 ms·

One other is Fossil: https://www.fossil-scm.org/home/doc/trunk/www/index.wiki https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

by pwg 8y ago

Something1234 8y ago
Are you using it?
- pwg 8y ago
  Myself, no, but that has as much to do with the fact that I started using git long ago before either Fossil existed or before I learned of its existence. But to be fair, the OP's question did not ask "what are you using" but rather "what else is out there". Referencing Fossil is valid for a "what else is out there" query, even if one is not, at present, using Fossil. I have looked at it from time to time, and having a whole turnkey "github like" interface all in one program is a nice feature that has its appeal. But I have not had a need for all of that (yet) so I have not made much use of it beyond experimenting.
Lowkeyloki 8y ago
I want so much to like Fossil. But I feel like it's too closely tailored to Dwayne Hipp's workflow. I'm also not so hot on the jack of all trades approach of the built-in issue tracker, wiki, etc. It goes against my Unix philosophy sensibilities. But that's just my 2¢.
zebproj 8y ago
I am a casual user of Fossil. I tried it out for some of my smaller projects. I can't say I am at the point where I "get" it, but I'd definitely recommend at least trying it out, as it provides a contrasting perspective to source control (from git). The integrated Wiki and ticketing system can be very helpful. The built-in web interface is definitely convenient. Also, the codebase is written in very clean C code (it's written by the SQLite devs, so I expect no less from them). It is very easy to compile from source. Also, the documentation they have is quite nice. I definitely struggle with parts of Fossil. Fossil does not make it easy to revise commits (this is an intentional design). I one time made a commit on a badly time-skewed machine and it took me all day to look up how to correct that (but I found it in their documentation). I'm also still getting the hang of how branching works in Fossil. It is very hard to have a massive amount of contributors to code. Again, this is another intentional design choice. It's certainly not a VCS for all projects. But for certain kinds of projects, it really works well.
LVB 8y ago
I used it for personal projects for a while. The built in Wiki and history viewer were actually pretty useful, but I found the limitations on history mutations pretty annoying. My view is that especially for a local, personal project, I should be able to maintain things however I want. Alas, back to git.

One other is Fossil: https://www.fossil-scm.org/home/doc/trunk/www/index.wiki https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

by pwg 8y ago

One other is Fossil: https://www.fossil-scm.org/home/doc/trunk/www/index.wiki https://www.fossil-scm.org/home/doc/trunk/www/index.wiki

Something1234 8y ago

Are you using it?

pwg 8y ago
Myself, no, but that has as much to do with the fact that I started using git long ago before either Fossil existed or before I learned of its existence. But to be fair, the OP's question did not ask "what are you using" but rather "what else is out there". Referencing Fossil is valid for a "what else is out there" query, even if one is not, at present, using Fossil. I have looked at it from time to time, and having a whole turnkey "github like" interface all in one program is a nice feature that has its appeal. But I have not had a need for all of that (yet) so I have not made much use of it beyond experimenting.

Lowkeyloki 8y ago

I want so much to like Fossil. But I feel like it's too closely tailored to Dwayne Hipp's workflow. I'm also not so hot on the jack of all trades approach of the built-in issue tracker, wiki, etc. It goes against my Unix philosophy sensibilities. But that's just my 2¢.

zebproj 8y ago

I am a casual user of Fossil. I tried it out for some of my smaller projects. I can't say I am at the point where I "get" it, but I'd definitely recommend at least trying it out, as it provides a contrasting perspective to source control (from git). The integrated Wiki and ticketing system can be very helpful. The built-in web interface is definitely convenient. Also, the codebase is written in very clean C code (it's written by the SQLite devs, so I expect no less from them). It is very easy to compile from source. Also, the documentation they have is quite nice. I definitely struggle with parts of Fossil. Fossil does not make it easy to revise commits (this is an intentional design). I one time made a commit on a badly time-skewed machine and it took me all day to look up how to correct that (but I found it in their documentation). I'm also still getting the hang of how branching works in Fossil. It is very hard to have a massive amount of contributors to code. Again, this is another intentional design choice. It's certainly not a VCS for all projects. But for certain kinds of projects, it really works well.

LVB 8y ago

I used it for personal projects for a while. The built in Wiki and history viewer were actually pretty useful, but I found the limitations on history mutations pretty annoying. My view is that especially for a local, personal project, I should be able to maintain things however I want. Alas, back to git.