git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 03/10] glossary: expand and clarify some definitions, prune cross-references
Date: Thu, 17 May 2007 00:30:40 -0400	[thread overview]
Message-ID: <20070517043040.GA5032@fieldses.org> (raw)
In-Reply-To: <f2a4b4$ein$3@sea.gmane.org>

On Mon, May 14, 2007 at 07:00:48PM +0200, Jakub Narebski wrote:
> J. Bruce Fields wrote:
> 
> > +[[def_detached_HEAD]]detached HEAD::
> > +       Normally HEAD refers to the tip of a
> > +       <<def_branch,branch>>.
> 
> Normally HEAD refers to the branch _name_ (names current branch).
> From this sentence one can think that normally HEAD is pointer
> to commit which is tip of current branch.

OK, thanks; fixed in maint branch of
git://linux-nfs.org/~bfields/git.git.

--b.

  reply	other threads:[~2007-05-17  4:30 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <11791560893572-git-send-email->
2007-05-14 15:21 ` [PATCH 02/10] user-manual: revise birdseye-view chapter J. Bruce Fields
2007-05-15  0:07   ` Junio C Hamano
2007-05-15  2:58     ` J. Bruce Fields
     [not found] ` <1179156089759-git-send-email->
2007-05-14 15:21   ` [PATCH 03/10] glossary: expand and clarify some definitions, prune cross-references J. Bruce Fields
2007-05-14 17:00     ` Jakub Narebski
2007-05-17  4:30       ` J. Bruce Fields [this message]
     [not found]   ` <11791560893022-git-send-email->
2007-05-14 15:21     ` [PATCH 04/10] user-manual: move quick-start to an appendix J. Bruce Fields
     [not found]     ` <11791560891179-git-send-email->
2007-05-14 15:21       ` [PATCH 05/10] Documentation: remove howto's now incorporated into manual J. Bruce Fields
     [not found]       ` <1179156089470-git-send-email->
2007-05-14 15:21         ` [PATCH 06/10] user-manual: move howto/make-dist.txt into user manual J. Bruce Fields
     [not found]         ` <11791560892667-git-send-email->
2007-05-14 15:21           ` [PATCH 07/10] user-manual: move howto/using-topic-branches into manual J. Bruce Fields
     [not found]           ` <11791560901-git-send-email->
2007-05-14 15:21             ` [PATCH 08/10] user-manual: add a "counting commits" example J. Bruce Fields
     [not found]             ` <11791560901645-git-send-email->
2007-05-14 15:21               ` [PATCH 09/10] user-manual: introduce git J. Bruce Fields
     [not found]               ` <1179156090113-git-send-email->
2007-05-14 15:21                 ` [PATCH 10/10] user-manual: listing commits reachable from some refs not others J. Bruce Fields
2007-05-14 16:30             ` [PATCH 07/10] user-manual: move howto/using-topic-branches into manual Luck, Tony
2007-05-14 17:11               ` [PATCH] user-manual: fix origin/linus confusion in topic-branches example J. Bruce Fields
2007-05-14 17:44           ` [PATCH 06/10] user-manual: move howto/make-dist.txt into user manual Linus Torvalds
2007-05-14 21:39             ` J. Bruce Fields

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=20070517043040.GA5032@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).