Imagine seeing your command failing with "too many arguments" when you run "git cmd foo bar baz". Can you tell it will work if you said "git cmd foo bar"? Or is that trimming your command line too much? Too little? You cannot quite tell. If the command reported "unknown argument: 'bar'", you would know that among the arguments you gave to "git", i.e. "cmd foo bar baz", up to "cmd foo" were understood and "bar" and "baz" were not. This was one of the things I noticed while reviewing a topic and marked as leftoverbits to be cleaned up after the dust settled. The dust has settled and it is a good time to clean them up. Junio C Hamano (4): refs: avoid "too many arguments" cat-file: avoid "too many arguments" notes: avoid "too many arguments" miscellaneous: avoid "too many arguments" builtin/cat-file.c | 3 ++- builtin/notes.c | 18 +++++++++--------- builtin/prune-packed.c | 6 +++--- builtin/receive-pack.c | 3 ++- builtin/refs.c | 4 +++- builtin/tag.c | 2 +- t/t1006-cat-file.sh | 8 +++++--- t/t1460-refs-migrate.sh | 7 ++++--- t/t3301-notes.sh | 2 +- 9 files changed, 30 insertions(+), 23 deletions(-) -- 2.46.0-235-g968ce1ce0e
