How big is a Git commit?

(ratfactor.com)

27 points | by theanonymousone 2 days ago

5 comments

  • nathanpankon 1 hour ago
    I played with making a git alternative that was streamlined according to workflow. I haven't completely abandoned it, but my core idea was that you can use ast path to compress the data further.

    Like you said git is really efficient, and even though I went in with some criticism because of the work(mess) that is chromium and the deep hacking I did there to fix stuff between versions without forcing a complete rebuild

    I came to the conclusion that as a compression alternative, my approach wasn't worth it. Git did a better job!

    Anyway here's the attempt: https://github.com/pankon/gat

    • Anduia 1 hour ago
      It is not public is it?
      • nathanpankon 19 minutes ago
        Good call, made it public :)

        Thanks!

  • cocoto 1 hour ago
    > The du options are: s to summarize and b to display bytes.

    Small nitpick: Use long options and your code samples become self explanatory!

    • NetOpWibby 31 minutes ago
      I always use long options when possible. I don’t need terseness, computers do. I wanna help future me figure out how to run something.
  • fiddlerwoaroof 2 hours ago
    It can get even smaller when loose objects get packed into packfiles because of delta compression: a whole bunch of identical files can be stored in minimal overhead over storing one copy.
    • bewuethr 21 minutes ago
      I think the 250 files all containing just "foo" are stored as a single blob, too, even before creating a packfile.
  • grumbelbart2 1 hour ago
    Did you do —apparent-size?
  • llj123 2 hours ago
    [dead]