4 ms·

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 fr

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.

bch 9y ago
> 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.
- fermuch 9y ago
  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.
  - Boulth 9y ago
    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 https://github.com/google/git-appraise
bch 9y ago
> 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 https://www.fossil-scm.org/xfer/doc/trunk/www/tickets.wiki

bch 9y ago

> 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.

fermuch 9y ago
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.
- Boulth 9y ago
  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 https://github.com/google/git-appraise

bch 9y ago

> 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 https://www.fossil-scm.org/xfer/doc/trunk/www/tickets.wiki