I think it would be helpful (in determining the size of this problem) to determine the commands that should grow an option to show paths relatively.
Obviously, "status" is the primary target, but essentially anything that outputs file paths could also be considered ("conflicts" being one that springs to mind).
What about commands like "update"? If I run an update, it lists the files affected. However, I think one distinction to make is that while "status" and "conflicts" produce repeatable output, "update" does not. Its output is more informational than being the purpose of the command itself.
So my thought is that we should be looking at commands that have the core purpose of outputting paths to files, and looking at adding an option to those. Commands that output paths to files as information about some larger task are out of scope I think.
I think it would be helpful (in determining the size of this problem) to determine the commands that should grow an option to show paths relatively.
Obviously, "status" is the primary target, but essentially anything that outputs file paths could also be considered ("conflicts" being one that springs to mind).
What about commands like "update"? If I run an update, it lists the files affected. However, I think one distinction to make is that while "status" and "conflicts" produce repeatable output, "update" does not. Its output is more informational than being the purpose of the command itself.
So my thought is that we should be looking at commands that have the core purpose of outputting paths to files, and looking at adding an option to those. Commands that output paths to files as information about some larger task are out of scope I think.