From mboxrd@z Thu Jan  1 00:00:00 1970
From: Junio C Hamano <junkio@cox.net>
Subject: Re: How to create and keep up to date a naked/bare repository?
Date: Fri, 27 Jan 2006 13:00:11 -0800
Message-ID: <7vek2t1j50.fsf@assigned-by-dhcp.cox.net>
References: <7v1wyvn9pc.fsf@assigned-by-dhcp.cox.net>
	<7vd5ie735a.fsf@assigned-by-dhcp.cox.net>
	<m34q3p7q1n.fsf@localhost.localdomain>
	<7v3bj9344w.fsf@assigned-by-dhcp.cox.net>
	<20060127190157.GF23949@fieldses.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: git@vger.kernel.org
X-From: git-owner@vger.kernel.org Fri Jan 27 22:00:24 2006
Return-path: <git-owner@vger.kernel.org>
Envelope-to: gcvg-git@gmane.org
Received: from vger.kernel.org ([209.132.176.167])
	by ciao.gmane.org with esmtp (Exim 4.43)
	id 1F2ahd-0006Qt-WA
	for gcvg-git@gmane.org; Fri, 27 Jan 2006 22:00:18 +0100
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932501AbWA0VAO (ORCPT <rfc822;gcvg-git@m.gmane.org>);
	Fri, 27 Jan 2006 16:00:14 -0500
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S932500AbWA0VAO
	(ORCPT <rfc822;git-outgoing>); Fri, 27 Jan 2006 16:00:14 -0500
Received: from fed1rmmtao01.cox.net ([68.230.241.38]:29107 "EHLO
	fed1rmmtao01.cox.net") by vger.kernel.org with ESMTP
	id S932501AbWA0VAM (ORCPT <rfc822;git@vger.kernel.org>);
	Fri, 27 Jan 2006 16:00:12 -0500
Received: from assigned-by-dhcp.cox.net ([68.4.9.127])
          by fed1rmmtao01.cox.net
          (InterMail vM.6.01.05.02 201-2131-123-102-20050715) with ESMTP
          id <20060127205910.TABR15695.fed1rmmtao01.cox.net@assigned-by-dhcp.cox.net>;
          Fri, 27 Jan 2006 15:59:10 -0500
To: "J. Bruce Fields" <bfields@fieldses.org>
User-Agent: Gnus/5.110004 (No Gnus v0.4) Emacs/21.4 (gnu/linux)
Sender: git-owner@vger.kernel.org
Precedence: bulk
X-Mailing-List: git@vger.kernel.org
Archived-At: <http://permalink.gmane.org/gmane.comp.version-control.git/15188>

"J. Bruce Fields" <bfields@fieldses.org> writes:

>> Maybe somebody so inclined could copyedit it, find an
>> appropriate place for it somewhere in the tutorial.txt or
>> core-tutorial.txt and feed that back to me in a patch form.
>> Hint, hint,... ;-).
>
> It might make sense just to dump it in Documentation/howto/ for now.

Perhaps, but I forgot to say "after some discussion".

I think people on the list have better suggestion than what I
outlined, and I suspect I probably have some details wrong in
that message.