From: Junio C Hamano <gitster@pobox.com>
To: Dragan Simic <dsimic@manjaro.org>
Cc: Hugo Sales <hugo@hsal.es>,
git@vger.kernel.org, Derrick Stolee <derrickstolee@github.com>,
Shaoxuan Yuan <shaoxuan.yuan02@gmail.com>
Subject: Re: [PATCH 0/3] Add `-p' option to `git-mv', inspired by `mkdir'
Date: Tue, 31 Oct 2023 14:58:09 +0900 [thread overview]
Message-ID: <xmqq5y2n49la.fsf@gitster.g> (raw)
In-Reply-To: <ffbb04b363938e4a487906134ce4f3c6@manjaro.org> (Dragan Simic's message of "Tue, 31 Oct 2023 05:54:31 +0100")
Dragan Simic <dsimic@manjaro.org> 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?
next prev parent reply other threads:[~2023-10-31 6:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 23:34 [PATCH 0/3] Add `-p' option to `git-mv', inspired by `mkdir' Hugo Sales
2023-10-09 23:34 ` [PATCH 1/3] mv: Add -p option to create parent directories Hugo Sales
2023-10-09 23:34 ` [PATCH 2/3] mv: Add tests for new -p flag Hugo Sales
2023-10-09 23:34 ` [PATCH 3/3] mv: Add documentation for new `-p' flag Hugo Sales
2023-10-10 0:39 ` [PATCH 0/3] Add `-p' option to `git-mv', inspired by `mkdir' Junio C Hamano
2023-10-10 0:59 ` Junio C Hamano
2023-10-11 12:33 ` Hugo Sales
2023-10-31 4:30 ` Junio C Hamano
2023-10-31 4:54 ` Dragan Simic
2023-10-31 5:58 ` Junio C Hamano [this message]
2023-10-31 6:38 ` Dragan Simic
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqq5y2n49la.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=derrickstolee@github.com \
--cc=dsimic@manjaro.org \
--cc=git@vger.kernel.org \
--cc=hugo@hsal.es \
--cc=shaoxuan.yuan02@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.