News for hackers. Stuff that matters.
Re:Git’s database internals I: packed object store by eminence32 on Monday August 29, 2022 @01:45PM (#32641178)
When you rename a file in git, you can get a glimps of its internal model -- renames are not explicitly tracked. Since git only stores full copies of each object, it has to employ heuristics to figure out if a (deleted file, created file) pair should be considered a rename. This is why you sometimes see a percentage next to a rename in a "git log" -- this is git's internal metric about how similar/dissimilar the files are.
Re:Git’s database internals I: packed object store by rossmohax on Monday August 29, 2022 @05:42PM (#32643931)
Is there any value in first class renames other than some performance boost ?
Re:Git’s database internals I: packed object store by dlkmp on Tuesday August 30, 2022 @08:16AM (#32649377)
I'd argue yes. I remember times where I was puzzled that some config file had been deleted (in a commit touching lots of files) only to find out after some analysis that is was simply moved/ renamed.