From: "Octavio Alvarez" <alvarezp@alvarezp.ods.org>
To: "Ron Garret" <ron1@flownet.com>, git@vger.kernel.org
Subject: Re: What does git reset do?
Date: Tue, 02 Feb 2010 00:37:10 -0800 [thread overview]
Message-ID: <op.u7hrj8vb4oyyg1@localhost.localdomain> (raw)
In-Reply-To: <ron1-2B8474.00242602022010@news.gmane.org>
On Tue, 02 Feb 2010 00:24:26 -0800, Ron Garret <ron1@flownet.com> wrote:
> In article <op.u7hpv8nd4oyyg1@localhost.localdomain>,
> "Octavio Alvarez" <alvarezp@alvarezp.ods.org> wrote:
>
>> > So... what does git reset do?
>>
>> Sets the current head (and branch, if not detached) to the specified
>> commit...
>
> Ah. It's the "and branch" part that I was missing. Thanks!
>
> Hm... maybe "detached head" is not as inappropriate a term as I first
> thought. When you checkout a branch, HEAD really is "attached" to the
> branch insofar as the branch head gets "dragged along" on commits and
> resets. (Have I got that right?)
99% right. I'm just not sure if there is such thing as "branch head".
You may compare the branch with a "moving tag", in which case the branch
is just a pointer, so "branch head" would be redundant, and besides "HEAD"
is an already used term. So you may say simply "branch" instead.
But it's easy intuitive to compare it with a bunch of related commits,
each parent of another. And gitk also has a line that says "branch: _____,
______, ______" for each commit.
In any case, it's just a matter of getting the terms to match the
developers'.
--
--
Octavio.
next prev parent reply other threads:[~2010-02-02 8:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 7:47 What does git reset do? Ron Garret
2010-02-02 8:01 ` Octavio Alvarez
2010-02-02 8:24 ` Ron Garret
2010-02-02 8:37 ` Octavio Alvarez [this message]
2010-02-02 15: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=op.u7hrj8vb4oyyg1@localhost.localdomain \
--to=alvarezp@alvarezp.ods.org \
--cc=git@vger.kernel.org \
--cc=ron1@flownet.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).