On Mon, Dec 1, 2014 at 4:04 AM, Junio C Hamano <gits...@pobox.com> wrote: > > If I were redoing this today, I would probably nominate the "git" > potty as such a "kitchen synk" command. We have "--man-path" that > shows the location of the manual pages, "--exec-path[=path]" that > either shows or allows us to override the path to the subcommands, > and "--show-prefix", "--show-toplevel", and friends may feel quite > at home there.
I wonder if we could reuse "git config" which is already a "kitchen synk" command to get/set a lot of parameters. Maybe we could dedicate a "git" or "virtual" or "proc" or "sys" (like /proc or /sys in Linux) namespace for these special config parameters that would not necessarily reflect something in the config file. "git config git.man-path" would be the same as "git --man-path". "git config git.root" would be the same as "git rev-parse --show-toplevel". "git config git.exec-path mypath" would allow us to override the path to the subcommands, probably by saving something in the config file. If we wanted for example to try just once a special exec-path we could use: git -c git.exec-path=/path/to/git-foo foo Best, Christian. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
