On 2023-10-31 06:58, Junio C Hamano wrote:
Dragan Simic <dsimic@xxxxxxxxxxx> writes:
A quite similar ambiguity exists in cp(1) in mv(1), which is also
resolved by the use of the trailing slash character. However, I've
encountered only one person aware of that disambiguation, and in cp(1)
only, but in the "I always include the trailing slash" way, without
actually understanding it fully. Maybe I need to encounter more
people, I don't know.
If the majority of (perhaps new) users you already know find such
disambiguation method unfamiliar, that already is a good anecdata
without any need for you to meet more people to tell us that it is
not a very easy-to-understand thing for them, no?
Quite frankly, I'm divided there. On the one hand, you're right that
this disambiguation method is a bit confusing and it's absolutely not
very well known. On the other hand, it's already out there in the wild,
including git, and it's actually quite useful when used properly.
If I had to vote, I'd give my vote to embracing this disambiguation
method, but only with good documentation and some kind of education
through an article or two. I believe that proper education simply isn't
present, or at least not in a user-friendly manner, which should be
corrected, regardless of the new "git mv -p" feature being accepted or
not.
