shejialuo <shejialuo@xxxxxxxxx> writes: > If so, we would make "git refs list" to place "git for-each-ref" at > all. However, in the current implementation, we indeed introduce > duplicate code path if we decide to do above. I do not know what you meant by your first sentence. If you make "git refs list <anything>" a thin wrapper for "git for-each-ref <anthing>", you can satisfy "I want to teach any and all features related to references to the 'git refs' command" while not penalizing existing users. After all, that is essentially what "git branch" and "git tag" do as their listing mode and supports the featurs from for-each-ref, isn't it?
