From: Mathieu Chouquet-Stringer <ml2news@free.fr>
To: junkio@cox.net (Junio C Hamano)
Cc: git@vger.kernel.org
Subject: Re: How to create and keep up to date a naked/bare repository?
Date: 26 Jan 2006 19:27:30 +0100 [thread overview]
Message-ID: <m34q3q9759.fsf@localhost.localdomain> (raw)
In-Reply-To: <7v64o7fac1.fsf@assigned-by-dhcp.cox.net>
junkio@cox.net (Junio C Hamano) writes:
> 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
I guess I'm a little bit confused here as I'm not quite sure what I'm
trying to accomplish...
Here's what I ran:
% GIT_DIR=. git fetch \
--update-head-ok git://www.kernel.org/pub/scm/git/git master:master
Isn't git supposed to fetch master:origin as my remotes/origin file
contains (I actually tried both and refs/heads/origin and refs/heads/master
have the same value):
URL: git://www.kernel.org/pub/scm/git/git.git
Pull: master:origin
Pull: todo:todo
Pull: html:html
Pull: maint:maint
Pull: man:man
Pull: pu:pu
So it knows about the repository and the ref spec so all I need would be
the --update-head-ok flag then, no?
--
Mathieu Chouquet-Stringer
"Le disparu, si l'on vénère sa mémoire, est plus présent et
plus puissant que le vivant".
-- Antoine de Saint-Exupéry, Citadelle --
next prev parent reply other threads:[~2006-01-26 18:27 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
2006-01-26 15:11 ` Mathieu Chouquet-Stringer
2006-01-26 18:27 ` Mathieu Chouquet-Stringer [this message]
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=m34q3q9759.fsf@localhost.localdomain \
--to=ml2news@free.fr \
--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).