From: Junio C Hamano <junkio@cox.net>
To: Mathieu Chouquet-Stringer <ml2news@free.fr>
Cc: git@vger.kernel.org
Subject: Re: How to create and keep up to date a naked/bare repository?
Date: Thu, 26 Jan 2006 04:22:06 -0800 [thread overview]
Message-ID: <7v64o7fac1.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <m37j8n9rat.fsf_-_@localhost.localdomain> (Mathieu Chouquet-Stringer's message of "26 Jan 2006 12:12:10 +0100")
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
next prev parent reply other threads:[~2006-01-26 12:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 13:00 [RFD] remembering hand resolve Junio C Hamano
2006-01-25 13:45 ` Andreas Ericsson
2006-01-25 23:56 ` Junio C Hamano
2006-01-26 11:12 ` How to create and keep up to date a naked/bare repository? Mathieu Chouquet-Stringer
2006-01-26 12:22 ` Junio C Hamano [this message]
2006-01-26 15:11 ` Mathieu Chouquet-Stringer
2006-01-26 18:27 ` Mathieu Chouquet-Stringer
2006-01-27 3:36 ` Junio C Hamano
2006-01-27 10:30 ` Refs naming after clone (was: Re: How to create and keep up to date a naked/bare repository?) Josef Weidendorfer
2006-01-27 13:34 ` How to create and keep up to date a naked/bare repository? Mathieu Chouquet-Stringer
2006-01-27 18:41 ` Junio C Hamano
2006-01-27 19:01 ` J. Bruce Fields
2006-01-27 21:00 ` Junio C Hamano
2006-01-29 9:10 ` [PATCH/RFC] git-rerere: reuse recorded resolve Junio C Hamano
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=7v64o7fac1.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=ml2news@free.fr \
/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).