linux-kernel - Re: [ANNOUNCE] GIT 1.6.4.rc1

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 15 Jul 2009 23:55:41 -0700
From:	Junio C Hamano <gitster@...ox.com>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	git@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>
Subject: Re: [ANNOUNCE] GIT 1.6.4.rc1

Jeff Garzik <jeff@...zik.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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/