> It's not about managing a library of any kind, it's about a tree of changes.
No, a Git repo is not "a tree of changes" (nor is Git a "hacky diffing tool").
> It's not about managing a library of any kind, it's about a tree of changes.
No, a Git repo is not "a tree of changes" (nor is Git a "hacky diffing tool").
Define Git for me then please. Obviously we're using very different tools. Git itself, for me, manages diffs (or rather refs of diffs) as a tree. Branches are pointers. That's it.
/e: and why on earth is it an algebra about publishing? As I said before, imho it's not about publishing, but about tracking. Publishing is just an aspect.
I'll pass.
> Git [...] manages diffs (or rather refs of diffs)
Wrong.
> why on earth is it an algebra about publishing?
It's not. I said operations on a repo comprise an algebra of publishing. As for why? Because that's what we're talking about: the stupid content tracker. This is not disputable.
> As I said before, imho it's [...] about tracking
You didn't say that. And you were less than humble about what you did say.