From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jeff Garzik Subject: Re: [ANNOUNCE] GIT 1.6.4.rc1 Date: Thu, 16 Jul 2009 02:43:21 -0400 Message-ID: <4A5ECC09.3010405@garzik.org> References: <7vmy75bg2f.fsf@alter.siamese.dyndns.org> <4A5EA598.5050801@garzik.org> <7v3a8xb0lz.fsf@alter.siamese.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: git@vger.kernel.org, LKML To: Junio C Hamano X-From: git-owner@vger.kernel.org Thu Jul 16 08:45:54 2009 Return-path: Envelope-to: gcvg-git-2@gmane.org Received: from vger.kernel.org ([209.132.176.167]) by lo.gmane.org with esmtp (Exim 4.50) id 1MRKj3-0007EK-9f for gcvg-git-2@gmane.org; Thu, 16 Jul 2009 08:45:53 +0200 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1756869AbZGPGpG (ORCPT ); Thu, 16 Jul 2009 02:45:06 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1752418AbZGPGpG (ORCPT ); Thu, 16 Jul 2009 02:45:06 -0400 Received: from srv5.dvmed.net ([207.36.208.214]:55167 "EHLO mail.dvmed.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751811AbZGPGpF (ORCPT ); Thu, 16 Jul 2009 02:45:05 -0400 Received: from cpe-069-134-158-197.nc.res.rr.com ([69.134.158.197] helo=bd.yyz.us) by mail.dvmed.net with esmtpsa (Exim 4.69 #1 (Red Hat Linux)) id 1MRKiF-0006fJ-4G; Thu, 16 Jul 2009 06:45:03 +0000 User-Agent: Thunderbird 2.0.0.21 (X11/20090320) In-Reply-To: <7v3a8xb0lz.fsf@alter.siamese.dyndns.org> X-Spam-Score: -4.4 (----) X-Spam-Report: SpamAssassin version 3.2.5 on srv5.dvmed.net summary: Content analysis details: (-4.4 points, 5.0 required) Sender: git-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: git@vger.kernel.org Archived-At: Junio C Hamano wrote: > Jeff Garzik writes: > >> Is there some sort of guide to the new best practices for handling >> trees such as git.kernel.org, where one pushes into "foo.git" >> directly, and there is no checked-out source code at all? > > I think old repositories will be helped if you add > > [core] > bare > > to their foo.git/config files. Thanks. What about cloning new repositories? Real world example: Local workstation has /spare/repo/cld/.git repository, with checked-out working tree. 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 -- even though there are no checked-out files. The checked-out files were not copied in the scp. Regards, Jeff