Re:Why Google Stores Billions of Lines of Code in a Single R...
by ghosty141 on Sunday February 12, 2023 @06:15PM
(#34768216)
How do you deal with wanting to see the history, graph etc of just one sub-project? Does the tooling handle this?
[ Parent
| on HN ]
Re:Why Google Stores Billions of Lines of Code in a Single R...
by aleksiy123 on Sunday February 12, 2023 @06:20PM
(#34768255)
I believe everything is tracked at the folder/file level and not a project level. I'm not sure there even is a concept of a project. But maybe someone can correct me.
Re:Why Google Stores Billions of Lines of Code in a Single R...
by ASinclair on Sunday February 12, 2023 @08:52PM
(#34769268)
There is a concept of a project. Though viewing change history is more organized around packages and files.
Re:Why Google Stores Billions of Lines of Code in a Single R...
by dastbe on Sunday February 12, 2023 @06:26PM
(#34768304)
git log <directory> accomplishes this already.
Re:Why Google Stores Billions of Lines of Code in a Single R...
by myko on Sunday February 12, 2023 @06:46PM
(#34768446)
Google uses piper and perforce (well, g4) before that
Re:Why Google Stores Billions of Lines of Code in a Single R...
by saagarjha on Sunday February 12, 2023 @09:57PM
(#34769651)
History for folders is visible in code search, it’s basically equivalent to what GitHub or Sourcegraph would give you. You can query dependencies from the build system. Anything beyond a couple levels deep is unlikely to load in any tools you have ;)