On Tue, 12 May 2015 20:34:01 -0700
Michael keybou...@gmail.com wrote:
[...]
I'm just not understanding the git reset -- it seems to not just
change the active branch, and possibly the working tree/cached for
commit, but also alters where branch label point.
That seems to be non-documented,
# keybou...@gmail.com / 2015-05-13 07:37:34 -0700:
These modes are selected by a special command line option: --soft,
--hard or --mixed, with the latter being the default.
The --soft option only repositions the branch's tip,
This is problem number one. That's pretty much what
Well, `git reset` is completely documented in its manual page
(try running `git help reset`).
I did. But ...
These modes are selected by a special command line option: --soft,
--hard or --mixed, with the latter being the default.
The --soft option only repositions the branch's tip,
On 2015-05-13, at 7:54 AM, Roman Neuhauser neuhau...@sigpipe.cz wrote:
# keybou...@gmail.com / 2015-05-13 07:37:34 -0700:
These modes are selected by a special command line option: --soft,
--hard or --mixed, with the latter being the default.
The --soft option only repositions the branch's
On Wed, 13 May 2015 08:29:39 -0700
Michael keybou...@gmail.com wrote:
[...]
Alright, maybe this is my first point of confusion.
I thought HEAD is where you are at -- which of those letters you
are pointing to. And, it may also be where a branch tip is pointing.
If I make a commit while
Michael keybou...@gmail.com writes:
those two sentences say the same thing. HEAD *is* the branch tip pointer,
unless it's detached.
Alright, maybe this is my first point of confusion.
I thought HEAD is where you are at -- which of those letters you are
pointing to.
And, it may also be
Michael keybou...@gmail.com writes:
keybounceMBP:config michael$ git commit -m First test
[animalAging 0653a0b] First test
1 file changed, 140 insertions(+)
create mode 100644 HarderWildlife.cfg
keybounceMBP:config michael$ gitk --all
^C
keybounceMBP:config michael$ git commit
