From: Alexey Zaytsev <alexey.zaytsev@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH] Let git remote accept up as alias to update
Date: Sat, 13 Dec 2008 21:18:56 +0300 [thread overview]
Message-ID: <20081213181704.20126.4200.stgit@zaytsev.su> (raw)
Signed-off-by: Alexey Zaytsev <alexey.zaytsev@gmail.com>
---
Don't know why, but I keep typing remote up instead of
remote update. As update is probably by far the most
used remote action, can we please have this alias?
builtin-remote.c | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/builtin-remote.c b/builtin-remote.c
index abc8dd8..8f5cd6d 100644
--- a/builtin-remote.c
+++ b/builtin-remote.c
@@ -893,7 +893,7 @@ int cmd_remote(int argc, const char **argv, const char *prefix)
result = show(argc, argv);
else if (!strcmp(argv[0], "prune"))
result = prune(argc, argv);
- else if (!strcmp(argv[0], "update"))
+ else if (!strcmp(argv[0], "update") || !strcmp(argv[0], "up"))
result = update(argc, argv);
else {
error("Unknown subcommand: %s", argv[0]);
next reply other threads:[~2008-12-13 18:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-13 18:18 Alexey Zaytsev [this message]
2008-12-14 11:25 ` [PATCH] Let git remote accept up as alias to update Jeff King
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=20081213181704.20126.4200.stgit@zaytsev.su \
--to=alexey.zaytsev@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).