From: Junio C Hamano <gitster@pobox•com>
To: Jeff Garzik <jeff@garzik•org>
Cc: git@vger•kernel.org, LKML <linux-kernel@vger•kernel.org>
Subject: Re: [ANNOUNCE] GIT 1.6.4.rc1
Date: Wed, 15 Jul 2009 23:55:41 -0700 [thread overview]
Message-ID: <7vocrl9kwi.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 4A5ECC09.3010405@garzik.org
Jeff Garzik <jeff@garzik•org> writes:
> I want to publish this tree to the world via a *.kernel.org-like
> system, so my task is to
>
> scp -r /spare/repo/cld/.git remote.example.com:/pub/scm/cld.git
>
> but if I do this with scp, then future pushes to
> remote.example.com:/pub/scm/cld.git emit the warning about updating
> the currently checked-out branch
I think "scp -r" is a wrong way to "clone", as it will copy .git/config
that is specific to your local work tree that does not apply to the
situation at remote.example.com anyway. You do not want to push into your
local repository with a work tree you are "scp -r"ing out of, but you do
want to push into the one at remote.example.com.
Interestingly enough, we had a two separate thread about making a bare
repository out of a repository with a work tree today ;-)
remote.example.com$ cd /pub/scm/
remote.example.com$ git clone --bare over.there:/spare/repo/cld/.git cld.git
next prev parent reply other threads:[~2009-07-16 6:56 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 0:57 [ANNOUNCE] GIT 1.6.4.rc1 Junio C Hamano
2009-07-16 3:51 ` Tommy Nordgren
2009-07-16 7:37 ` Mike Ralphson
2009-07-17 15:16 ` Tommy Nordgren
2009-07-16 3:59 ` Jeff Garzik
2009-07-16 6:31 ` Junio C Hamano
2009-07-16 6:43 ` Jeff Garzik
2009-07-16 6:45 ` Jeff Garzik
2009-07-16 6:48 ` Felipe Balbi
2009-07-16 7:17 ` Jeff Garzik
2009-07-16 7:21 ` Felipe Balbi
2009-07-16 6:55 ` Junio C Hamano [this message]
2009-07-16 7:15 ` Jeff Garzik
2009-07-16 7:27 ` Junio C Hamano
2009-07-16 20:19 ` Jeff Garzik
2009-07-16 6:55 ` [ANNOUNCE] " Nicolas Sebrecht
2009-07-18 23:05 ` [ANNOUNCE] " Nanako Shiraishi
2009-07-19 0:19 ` Junio C Hamano
2009-07-19 14:45 ` Nanako Shiraishi
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=7vocrl9kwi.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jeff@garzik$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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