that is a feature! You don't know how I miss that!
(that, and the handling of blobs)
that is a feature! You don't know how I miss that!
(that, and the handling of blobs)
Handling of blobs I can at least see preferring the differences, though git-lfs mostly acceptably shims that for me. The need to use git-lfs is definitely an annoyance, but it's another place where it's probably not a fatal flaw.
Or, to the extent that it arguably is, it would be when you're using git as something that it really, really isn't... it's a source code management tool. It's a good enough source code management tool that it's useful for many other things as well, like the way some people directly drive their personal websites with it. But it isn't a tool for managing lots of large files that can't be textually diffed, not a generic "content" management tool. I wouldn't expect git to necessarily store terabytes of video files, but then, it's not like Fossil is going to do that either from the sounds of it. git-lfs shims content blobs well enough to make it just an annoyance for source code management.
git --work-tree=/path/to/outputdir checkout HEAD -- subdirnameYep, handiest way to perform a first pass on narrowing down an introduced bug between a few commits.
Fossil has bisecting with much the same CLI as Git, for what that's worth.