From mboxrd@z Thu Jan  1 00:00:00 1970
From: Junio C Hamano <junkio@cox.net>
Subject: Re: [RFD] Git glossary: 'branch' and 'head' description
Date: Wed, 17 May 2006 12:57:32 -0700
Message-ID: <7v8xp0ctlf.fsf@assigned-by-dhcp.cox.net>
References: <e4f1ta$e07$1@sea.gmane.org>
	<7viro4ecao.fsf@assigned-by-dhcp.cox.net> <e4fsla$oth$1@sea.gmane.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: git@vger.kernel.org
X-From: git-owner@vger.kernel.org Wed May 17 21:57:46 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 1FgS9J-00027m-2Z
	for gcvg-git@gmane.org; Wed, 17 May 2006 21:57:37 +0200
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1751047AbWEQT5e (ORCPT <rfc822;gcvg-git@m.gmane.org>);
	Wed, 17 May 2006 15:57:34 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751069AbWEQT5e
	(ORCPT <rfc822;git-outgoing>); Wed, 17 May 2006 15:57:34 -0400
Received: from fed1rmmtao12.cox.net ([68.230.241.27]:41684 "EHLO
	fed1rmmtao12.cox.net") by vger.kernel.org with ESMTP
	id S1751047AbWEQT5d (ORCPT <rfc822;git@vger.kernel.org>);
	Wed, 17 May 2006 15:57:33 -0400
Received: from assigned-by-dhcp.cox.net ([68.4.9.127])
          by fed1rmmtao12.cox.net
          (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP
          id <20060517195733.BVEH27919.fed1rmmtao12.cox.net@assigned-by-dhcp.cox.net>;
          Wed, 17 May 2006 15:57:33 -0400
To: Jakub Narebski <jnareb@gmail.com>
In-Reply-To: <e4fsla$oth$1@sea.gmane.org> (Jakub Narebski's message of "Wed,
	17 May 2006 21:13:51 +0200")
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/20236>

Jakub Narebski <jnareb@gmail.com> writes:

> [cut long description]
>
> The description you gave is nice, but it belongs in Tutorial rather than in
> Glossary.

I suspect I was not clear enough for you when I said:

        I cannot easily do a glossary entry to describe that specific
        term, but maybe somebody else can split the following up and
        paraphrase.