From: "Dilip M" <dilipm79@gmail.com>
To: "Sitaram Chamarty" <sitaramc@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: user manual question
Date: Mon, 29 Dec 2008 12:03:51 +0530 [thread overview]
Message-ID: <c94f8e120812282233i3783cf65o5ad9663e079e7fd6@mail.gmail.com> (raw)
In-Reply-To: <slrnglg90m.olt.sitaramc@sitaramc.homelinux.net>
On Mon, Dec 29, 2008 at 6:42 AM, <sitaramc@gmail.com> wrote:
> On 2008-12-29, Zorba <cr@altmore.co.uk> wrote:
>> Hi Sitaram!
>>
>> Thanks for clearing that one up.
>
> you're welcome; we've all done a bit of struggling I guess!
>
>> Also, I did wonder about HEAD and head. One can move, the other
>> doesn't! (well, acually it does - head moves "forward", as the tip
>> of the branch grows)
>
> Here's an extract from my notes/internal talks on this:
>
> === basic concepts * a branch is "an active line of
> development" * //master//: default branch in a project, by
> convention * //head//: tip of a branch * a repo can track
> many branches, but the working tree is associated with only one
> branch at a time * //HEAD//: tip of the branch associated with
> the working tree; this is where commits go ** except
> when it's "detached"
That's a nice,compact and effective note. Thanks for sharing :-)
Consider pushing the full notes to GITHUB...would be _useful_ for all of
us..(like me)...
-- dm
next prev parent reply other threads:[~2008-12-29 6:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-28 11:07 user manual question Zorba
2008-12-28 14:38 ` Sitaram Chamarty
2008-12-28 16:36 ` Dilip M
2008-12-29 0:51 ` Zorba
2008-12-29 0:48 ` Zorba
2008-12-29 1:12 ` Sitaram Chamarty
2008-12-29 6:33 ` Dilip M [this message]
2008-12-29 16:38 ` Zorba
2008-12-29 17:18 ` Björn Steinbrink
2008-12-29 17:20 ` Markus Heidelberg
2008-12-29 17:27 ` Sitaram Chamarty
2008-12-29 19:30 ` Daniel Barkalow
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=c94f8e120812282233i3783cf65o5ad9663e079e7fd6@mail.gmail.com \
--to=dilipm79@gmail.com \
--cc=git@vger.kernel.org \
--cc=sitaramc@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).