Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes:
> Hence suggesting that the user just add "--" to resolve the ambiguity,
> as gitcli already discusses.
Sadly, requiring "--end-of-options" is a solution for a problem that
we didn't have to create. If we didn't take options written after
arg,
git rm --end-of-options foo -r
git rm foo ./-r
to force "-r" to be interpreted as a filename wouldn't have been
necessary. The presence of "foo" before "-r" would have been
sufficient.
I agree with you that, unfortunately, we'd need to teach a way (i.e.
"--" or "--end-of-options") to defeat this misguided GNUism in some
commands. Even if users stick to "options and then args", sadly,
they need to know it.
But we do already explain "--" and "--end-of-options" in gitcli.txt
so we should be OK.
