5 ms·

>>> [SVN] made an error I don't hear many other people mention where directories were checked out to revisions, rather than entire repositories. that is a feat

by _ZeD_ 7y ago

>>> [SVN] made an error I don't hear many other people mention where directories were checked out to revisions, rather than entire repositories. that is a feature! You don't know how I miss that! (that, and the handling of blobs)

shakna 7y ago
Git still let's you check out particular directories at particular commits. It's just a specialised usecase rather than the default. git --work-tree=/path/to/outputdir checkout HEAD -- subdirname
jerf 7y ago
I would check, double-check, and triple check whatever use case you miss that for. It is a serious misfeature, and I find any workflow that critically depends on it to be very likely a process smell. 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.
dev_north_east 7y ago
> that is a feature! You don't know how I miss that! Yep, handiest way to perform a first pass on narrowing down an introduced bug between a few commits.
- jerf 7y ago
  Have you used "git bisect"?
  - dev_north_east 7y ago
    Just reading up on it now. Seems interesting, might give it a shot next time.
    - jerf 7y ago
      In the case you mentioned of "just a few commits" it's of marginal utility, because you can do that manually almost as quickly, but it's a killer when it comes to "I don't really know when we introduced this" and you have to sift over thousands of commits. Unfortunately, it requires that you have the discipline to keep every commit on the relevant branches buildable (enough so to find the bugs), which is something you can do going forward but can't retroactively apply to a code base very well.
      - wyoung2 7y ago
        Agreed. Bisecting a deep and complex version history can be a lifesaver, especially under a time crunch. Fossil has bisecting with much the same CLI as Git, for what that's worth.

by _ZeD_ 7y ago

shakna 7y ago

Git still let's you check out particular directories at particular commits. It's just a specialised usecase rather than the default. git --work-tree=/path/to/outputdir checkout HEAD -- subdirname

jerf 7y ago

I would check, double-check, and triple check whatever use case you miss that for. It is a serious misfeature, and I find any workflow that critically depends on it to be very likely a process smell. 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.

dev_north_east 7y ago

> that is a feature! You don't know how I miss that! Yep, handiest way to perform a first pass on narrowing down an introduced bug between a few commits.

jerf 7y ago
Have you used "git bisect"?
- dev_north_east 7y ago
  Just reading up on it now. Seems interesting, might give it a shot next time.
  - jerf 7y ago
    In the case you mentioned of "just a few commits" it's of marginal utility, because you can do that manually almost as quickly, but it's a killer when it comes to "I don't really know when we introduced this" and you have to sift over thousands of commits. Unfortunately, it requires that you have the discipline to keep every commit on the relevant branches buildable (enough so to find the bugs), which is something you can do going forward but can't retroactively apply to a code base very well.
    - wyoung2 7y ago
      Agreed. Bisecting a deep and complex version history can be a lifesaver, especially under a time crunch. Fossil has bisecting with much the same CLI as Git, for what that's worth.