From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: git@vger.kernel.org
Subject: Renaming a remote is 'rename', but removing is 'rm'
Date: Wed, 05 Sep 2012 07:59:21 +0000 [thread overview]
Message-ID: <1346831961-ner-2892@calvin> (raw)
A fella on IRC was confused by $subject. And it did bother me sometimes as
well. If you don't use `git remote` often, it is confusing that the commands
are named inconsistently.
If I know that there is `git remote rm` then I kindof expect `git remote mv`
to exist. Because I am used to rm/mv and git rm/git mv as the standard unix
commands for renaming and removing something. On the other hand, if I know
that there is `git remote rename`, with the verb fully written out, I expect
`git remote delete/remove` to exist (or something similar, with the verb fully
written out).
Would there be any desire to make the subcommands more consistent in that
regard?
tom
next reply other threads:[~2012-09-05 8:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-05 7:59 Tomas Carnecky [this message]
2012-09-05 8:49 ` Renaming a remote is 'rename', but removing is 'rm' Nguyen Thai Ngoc Duy
2012-09-05 11:13 ` Matthieu Moy
2012-09-06 3:53 ` Junio C Hamano
2012-09-06 12:25 ` [PATCH] remote: prefer subcommand name 'remove' to 'rm' Nguyễn Thái Ngọc Duy
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=1346831961-ner-2892@calvin \
--to=tomas.carnecky@gmail.com \
--cc=git@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).