Comment on [deleted]

• nickwitha_k@lemmy.sdf.org ⁨6⁩ ⁨months⁩ ago

  Git isn’t very good with large binary files, git blame doubly so.

  Good point. I’d hope that there is some equivalent version control though.

  source

  • catloaf@lemm.ee ⁨6⁩ ⁨months⁩ ago

    There is git lfs as mentioned, and other systems like perforce support binaries too, but generally assets like those aren’t under the same kind of version control because they don’t change as frequently, aren’t worked on by multiple people, and can’t be diffed.

    source
  • ricecake@sh.itjust.works ⁨6⁩ ⁨months⁩ ago

    I think git lfs is a pretty well accepted tool for managing big files in git.

    source
  • v_krishna@lemmy.ml ⁨6⁩ ⁨months⁩ ago

    I think perforce is mostly used. There certainly should be a changelog but no text diff really.

    source
• Ledivin@lemmy.world ⁨6⁩ ⁨months⁩ ago

  That wouldn’t be difficult at all if it was in version control, just load them into an editor in a binary-search fashion. Even if it takes a few minutes per check, that shouldn’t take more than a few hours.

  source

  • ours@lemmy.world ⁨6⁩ ⁨months⁩ ago

    Assets are humongous compared to code and their tools probably integrate with more reasonable asset management solutions.

    source
• sajran@lemmy.ml ⁨6⁩ ⁨months⁩ ago

  You don’t need diffing to find something like that, bisect should handle this easily.

  source
• sajran@lemmy.ml ⁨6⁩ ⁨months⁩ ago

  You don’t need diffing to find something like that - bisect should be more than enough.

  source