News for hackers. Stuff that matters.
Re:The Fossil distributed version control system by coldacid on Saturday April 14, 2018 @11:14PM (#16840945)
One of the big things pushed with Fossil is that you get issues and a wiki built in, compared to Git, but when you consider it there's nothing preventing you from tracking issues and keeping wiki pages inside a Git repo as well. All that Fossil offers is some extra porcelain over its storage layer, which could be offered through extra tooling for Git as well.
Re:The Fossil distributed version control system by bch on Saturday April 14, 2018 @11:28PM (#16841010)
> All that Fossil offers is some extra porcelain over its storage layer...

Well... the tickets are things that live in the repository like a commit[0], so can reference other entries, and are referenceable by other entries, in a first class way. So “just porcelain“ or a “simple matter of programming” for git, in the dismissive sense.

[0] https://www.fossil-scm.org/xfer/doc/trunk/www/tickets.wiki

Re:The Fossil distributed version control system by bch on Saturday April 14, 2018 @11:24PM (#16840989)
> All that Fossil offers is some extra porcelain over its storage layer...

Well... the tickets are things that live in the repository like a commit, so can reference other entries, and are referenceable by other entries, in a first class way, so it’s a “simple matter of programming” for git in the dismissive sense.

Re:The Fossil distributed version control system by fermuch on Saturday April 14, 2018 @11:31PM (#16841020)
These features are possible right now on the backend of git to be implemented. There's nothing blocking git to add these things. What git would need is a front-end (remember, the cli is a frontend) to implement these.

Don't get me wrong, I do agree fossil is adding some new cards to the table. I just think it would be better implemented as extensions to git than a new system made from scratch.

Re:The Fossil distributed version control system by Boulth on Sunday April 15, 2018 @02:47AM (#16841576)
Yep, this is completely possible to implement in git. Fossil has it built-in already, that's good.

For anyone who wants to see what's possible using low level git tools: https://github.com/google/git-appraise