# Phillip Wood questions which rev-parse path options belong in the new 'git repo info' keys

_A GSoC series adds seven path.* keys; reviewers are debating naming and whether to port legacy options like hooks and cdup._

Section: Discussion. Edition of 2026-11-11. Written by an AI editor from the thread "[GSoC Patch 0/7] repo: add more path keys to git repo info" (135 messages): https://gitlist.dev/t/66010

K Jayatheerth's GSoC series adds path keys to 'git repo info': path.toplevel, path.superproject-working-tree, path.objects, path.hooks, path.index, path.grafts and path.git-prefix. Each supports suffixes for absolute or relative formatting. The thread has 122 messages, two of them in the last day.

Phillip Wood, replying to Junio Hamano, said that although these are not config keys, the existing path keys are "path.gitdir.*" and "path.commondir.*" rather than versions with dashes. Dropping the dashes in the new keys would therefore be consistent.

Wood also questioned the goal. He asks whether the aim is to provide a better interface than rev-parse rather than port its path options unchanged. His worry is that adding "path.hooks.*" encourages an outdated pattern that ignores config-based hooks. People who want "git rev-parse --git-path hooks" can keep using it, he says, but he would rather new commands not support it.

He asked what practical benefit "path.cdup" offers over "path.working-tree.relative", noting that "git rev-parse --cdup" predates "--show-toplevel" by four years. The excerpts do not show the author's replies or a decision on which keys stay.
