From: Junio C Hamano <junkio@cox.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [RFD] Git glossary: 'branch' and 'head' description
Date: Wed, 17 May 2006 12:57:32 -0700 [thread overview]
Message-ID: <7v8xp0ctlf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e4fsla$oth$1@sea.gmane.org> (Jakub Narebski's message of "Wed, 17 May 2006 21:13:51 +0200")
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.
next prev parent reply other threads:[~2006-05-17 19:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-17 11:37 [RFD] Git glossary: 'branch' and 'head' description Jakub Narebski
2006-05-17 18:28 ` Junio C Hamano
2006-05-17 19:13 ` Jakub Narebski
2006-05-17 19:57 ` Junio C Hamano [this message]
2006-05-17 20:06 ` Jakub Narebski
2006-05-19 6:53 ` David Kågedal
2006-05-19 9:21 ` Shawn Pearce
2006-05-20 0:28 ` Daniel Barkalow
2006-05-20 0:35 ` Junio C Hamano
2006-05-20 1:36 ` Daniel Barkalow
2006-05-20 2:06 ` Linus Torvalds
2006-05-21 1:01 ` Shawn Pearce
2006-05-21 8:30 ` Jakub Narebski
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=7v8xp0ctlf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--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).