From: Michael J Gruber <git@drmicha.warpmail.net>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: git@vger.kernel.org, gitster@pobox.com
Subject: Re: [PATCH] pull: mention "pull", not "fetch" in the error message.
Date: Fri, 26 Mar 2010 15:18:41 +0100 [thread overview]
Message-ID: <4BACC241.4010608@drmicha.warpmail.net> (raw)
In-Reply-To: <1269610699-13176-1-git-send-email-Matthieu.Moy@imag.fr>
Matthieu Moy venit, vidit, dixit 26.03.2010 14:38:
> For newbies who've just been taught "git push", the error message
Even though newbies don't read git.git's commit messages, you may want
to say "pull" here ;)
One way or the other, nothing beats the error messages in ident.c ;)
> "Where do you want to fetch from today?" is indeed confusing. Change it
> to "Where do you want to pull from today?" in case fetch was called from
> pull.
>
> Signed-off-by: Matthieu Moy <Matthieu.Moy@imag.fr>
> ---
> builtin/fetch.c | 6 +++++-
> git-pull.sh | 3 ++-
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> index 957be9f..f3246f5 100644
> --- a/builtin/fetch.c
> +++ b/builtin/fetch.c
> @@ -842,8 +842,12 @@ static int fetch_one(struct remote *remote, int argc, const char **argv)
> int ref_nr = 0;
> int exit_code;
>
> + char *cmd = getenv("GIT_USER_COMMAND");
> + if (cmd == NULL || cmd[0] == '\0')
> + cmd = "fetch";
> +
> if (!remote)
> - die("Where do you want to fetch from today?");
> + die("Where do you want to %s from today?", cmd);
>
> transport = transport_get(remote, NULL);
> transport_set_verbosity(transport, verbosity, progress);
> diff --git a/git-pull.sh b/git-pull.sh
> index 1a4729f..abc233b 100755
> --- a/git-pull.sh
> +++ b/git-pull.sh
> @@ -216,7 +216,8 @@ test true = "$rebase" && {
> done
> }
> orig_head=$(git rev-parse -q --verify HEAD)
> -git fetch $verbosity $progress --update-head-ok "$@" || exit 1
> +GIT_USER_COMMAND=pull \
> + git fetch $verbosity $progress --update-head-ok "$@" || exit 1
>
> curr_head=$(git rev-parse -q --verify HEAD)
> if test -n "$orig_head" && test "$curr_head" != "$orig_head"
next prev parent reply other threads:[~2010-03-26 14:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-26 13:38 [PATCH] pull: mention "pull", not "fetch" in the error message Matthieu Moy
2010-03-26 14:18 ` Michael J Gruber [this message]
2010-03-26 15:02 ` Matthieu Moy
2010-03-26 15:03 ` [PATCH v2] " Matthieu Moy
2010-03-26 23:12 ` Alex Riesen
2010-03-27 8:52 ` Matthieu Moy
2010-03-28 17:14 ` Junio C Hamano
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=4BACC241.4010608@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=Matthieu.Moy@imag.fr \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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 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).