Re: How to create and keep up to date a naked/bare repository?

From: Junio C Hamano <junkio@cox.net>
Date: Jan 26, 2006, 12:22 UTC
Message-ID: <7v64o7fac1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <m37j8n9rat.fsf_-_@localhost.localdomain>

Mathieu Chouquet-Stringer <ml2news@free.fr> writes:

> I can do a: GIT_DIR=. git fetch and it works.

That is the right way of doing it.

> The second question is I'd think I would have to use git fetch instead of
> git pull as a pull is fetch + merge and merging wouldn't make much sense as
> I didn't check out any files. Does it make any sense?

Absolutely. Bare repositories are either to be pushed into or fetched into.

> The third thing (can't reproduce ATM as I just got a fresh new clone) is
> that git fetch was just fetching over and over the same objects...

It sounds like you are not telling fetch to update the refs you track from outside. Perhaps, this may help (untested):

	$ GIT_DIR=/pub/scm/git/git.git git fetch \
        	--update-head-ok $remote master:master

$ 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.