Derrick Stolee <stolee@xxxxxxxxx> writes: > Teach Git the 'graph' builtin that will be used for writing and > reading packed graph files. The current implementation is mostly > empty, except for a check that the core.graph setting is enabled > and a '--pack-dir' option. Just to set my expectation straight. Is it fair to say that in the ideal endgame state, this will be like "git pack-objects" in that end users won't have to know about it, but would serve as a crucial building block that is invoked by other front-end commands that are more familiar to end users (just like pack-objects are used behind the scenes by repack, push, etc.)?