git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Pulling from refs/remotes/ ?

From
Han-Wen Nienhuys <hanwen@xs4all.nl>
Date
May 25, 2007, 01:35 UTC
Message-ID
<46563D55.3070607@xs4all.nl>
In-Reply-To
<7v7iqxvgx8.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano escreveu:
Show 29 quoted lines
> Han-Wen Nienhuys <hanwen@xs4all.nl> writes:
> 
>> why can't I pull from a remote?  I can do 
>>
>>   git log REMOTE-BRANCH
>>   git diff BRANCH REMOTE-BRANCH
>>
>> etc. But pulling yields
>>
>>  [hanwen@haring foobar]$ git pull . origin/nonrandr-setup
>>  error: no such remote ref refs/heads/origin/nonrandr-setup
>>  Fetch failure: .
>>
>> also, "Fetch failure: .", what is that supposed to mean?
> 
> You are treating your local repository as if it is a remote
> repository somewhere else, namely, '.' (current repository).
> 
> Notice "git log" and "git diff" are LOCAL operations?  "git
> pull" is "git fetch" which is a remote operation (i.e. it
> interacts with a remote repository) followed by "git merge"
> which is a local operation to merge in what was fetched or what
> you already have locally.
> 
> I think you would want:
> 
> 	git merge REMOTE-BRANCH
> 
> e.g. "git merge origin/nonrandr-setup".

Yes, that works, thanks. Wouldn't it be more consistent with this reasoning to disallow

  git pull . LOCAL-BRANCH 
too?

I still think that "fetch failure" is a bad error message. What information does it convey?

-- 
 Han-Wen Nienhuys - hanwen@xs4all.nl - http://www.xs4all.nl/~hanwen
Previous: Junio C HamanoNext: Junio C Hamano
Message 3 of 7 in “Pulling from refs/remotes/ ?”
  1. Han-Wen NienhuysMay 25, 2007
  2. Junio C HamanoMay 25, 2007
  3. Han-Wen NienhuysMay 25, 2007
  4. Junio C HamanoMay 25, 2007
  5. Han-Wen NienhuysMay 25, 2007
  6. Junio C HamanoMay 25, 2007
  7. Han-Wen NienhuysMay 26, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.