From: Mike Ralphson <mike.ralphson@gmail.com>
To: Matthieu Moy <Matthieu.Moy@imag.fr>
Cc: gitster@pobox.com, git@vger.kernel.org
Subject: Re: [PATCH] git-pull.sh: better warning message for "git pull" on detached head.
Date: Tue, 7 Apr 2009 10:24:35 +0100 [thread overview]
Message-ID: <e2b179460904070224o3057c6efk6930bd1249adb0fe@mail.gmail.com> (raw)
In-Reply-To: <1239052487-6936-1-git-send-email-Matthieu.Moy@imag.fr>
2009/4/6 Matthieu Moy <Matthieu.Moy@imag.fr>:
> Otherwise, git complains about not finding a branch to pull from in
> 'branch..merge', which is hardly understandable.
> + echo "You asked me to pull without telling me which branch you want"
> + echo "to merge with, and you are on a detached HEAD, so I cannot"
> + echo "know from 'branch.<branchname>.merge' in your configuration"
> + echo "file. Please name which branch you want to merge on the command"
'Know from' in this sense is a little confusing. Maybe something like:
s/so I cannot know from 'branch.<branchname>.merge' in your
configuration file/ \
so I cannot use any 'branch.<branchname>.merge' from your configuration file
?
> + echo "your configuration file does not tell me either. Please"
> + echo "name which branch you want to merge on the command line and"
> + echo "try again (e.g. 'git pull <repository> <refspec>')."
I know you haven't changed this part, but as it's included in the
patch, what we're asking the user to do is to 'specify' the branch to
merge, not to 'name' it.
Mike
next prev parent reply other threads:[~2009-04-07 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 21:14 [PATCH] git-pull.sh: better warning message for "git pull" on detached head Matthieu Moy
2009-04-07 9:24 ` Mike Ralphson [this message]
2009-04-07 9:56 ` [PATCH v2] " Matthieu Moy
2009-04-07 10:41 ` Finn Arne Gangstad
2009-04-07 11:36 ` Matthieu Moy
2009-04-08 0:43 ` Junio C Hamano
2009-04-08 7:24 ` [PATCH] " Matthieu Moy
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=e2b179460904070224o3057c6efk6930bd1249adb0fe@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--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).