From: Han-Wen Nienhuys <hanwen@xs4all.nl>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: Pulling from refs/remotes/ ?
Date: Sat, 26 May 2007 16:47:56 -0300 [thread overview]
Message-ID: <46588EEC.4080101@xs4all.nl> (raw)
In-Reply-To: <7vwsyxsit8.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano escreveu:
> And the reason it is "insane" is the same as why we currently do
> not interpret "git pull $repo origin/master" as a request to
> pull from remotes/origin/master. It really is none of your
> business what kind of remote branches the other end is
> interacting with.
fair enough; my remaining gripe is that the error message is broken.
My suggestion is to have
git fetch . XXX
(and by extension: pull) print something like
Will not fetch from self.
Do you mean "git merge XXX" or "git update-ref XXX" ?
It may be an artificial restriction when compared to "git pull $dir XXX"
but I think it helps the user better than "Fetch failure".
--
Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
prev parent reply other threads:[~2007-05-26 19:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-25 1:12 Pulling from refs/remotes/ ? Han-Wen Nienhuys
2007-05-25 1:19 ` Junio C Hamano
2007-05-25 1:35 ` Han-Wen Nienhuys
2007-05-25 1:53 ` Junio C Hamano
2007-05-25 2:24 ` Han-Wen Nienhuys
2007-05-25 3:06 ` Junio C Hamano
2007-05-26 19:47 ` Han-Wen Nienhuys [this message]
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=46588EEC.4080101@xs4all.nl \
--to=hanwen@xs4all.nl \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).