On Tue, 02 Feb 2010 00:24:26 -0800, Ron Garret <ron1@xxxxxxxxxxx> wrote:
In article <op.u7hpv8nd4oyyg1@xxxxxxxxxxxxxxxxxxxxx>,
"Octavio Alvarez" <alvarezp@xxxxxxxxxxxxxxxx> 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.
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html