From @jrdlph on Thu Dec 17 2015 22:45:57 GMT+0000 (UTC)
I have heard (and generally understand the notion that) ipfs has version control ‘built in’. I am wondering if anyone is actually using it for this specifically in the domain of source code revision control.
If so, how are you doing this? What sort of workflow are you employing to use IPFS to manage a revision history for your source code, and how are you ensuring that the whole history is maintained and accessible through IPFS?
When I first ran into IPFS, this was really the first thing I thought of: a dvcs where the continued availability of the code was sort of tied to how many people were interested in it, independent of some centralized host, but possibly backed by one to help maintain an official head commit and work contributions into it.
If an actual project exists that automates this with a specialized command line tool, I would definitely be interested in that too.
Edit I know there are git mirroring/rehosting tools out there, but I am more interested in leveraging ipfs natively as the core mechanism for composing source code revision histories.
Copied from original issue: https://github.com/ipfs/faq/issues/83