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

Re: how to properly update dumb-hosted repo (using rsync..?)

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 17, 2007, 23:46 UTC
Message-ID
<7v3au06g0r.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<9b3e2dc20712171511r41e6bd4p64d243747ad4d2af@mail.gmail.com>
"Stephen Sinclair" <radarsat1@gmail.com> writes:
Show 22 quoted lines
> $ git-pull
> Warning: No merge candidate found because value of config option
>          "branch.master.merge" does not match any remote branch fetched.
> No changes.
> -------------------
>
> However I haven't done any branching in this cloned repo, it is
> immediately after a git-clone from the web server.
>
> My .git/config basically looks like this, minus the "core" section:
>
> -------------------
> [remote "origin"]
>         url = http://my.server.com/git/project.git
>         fetch = +refs/heads/*:refs/remotes/origin/*
> [branch "master"]
>         remote = origin
>         merge = refs/heads/master
> -------------------
>
> Which seems fine to me...
> Any ideas?

A dumb question. does "git ls-remote origin" show what you expect to be there? Specifically, does refs/heads/master exist?

Previous: Stephen Sinclair
Message 2 of 2 in “how to properly update dumb-hosted repo (using rsync..?)”
  1. Stephen SinclairDec 17, 2007
  2. Junio C HamanoDec 17, 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.