Andy Parkins wrote:
Just because the virtual branch is stored in HEAD, I think it is dangerous to thing of HEAD as being the thing that is logged - it is this virtual branch that should be logged because that branch is always there and can be tracked through time as a discrete entity. If you track HEAD itself, then sometimes it will hold the same as a branch reflog, sometimes it will hold unique data.
hopefully, yes! Having to know "uhm, that time I was detached, oh, no, that was a ref" is the variable. The reflog we are talking about, no matter how it might be called or how its symbol is should track where my index wanders. which is called HEAD, I think (sorry, I'm quite new to git). So, to make it clear, when I do this: git checkout master git checkout build git checkout master~1 git checkout dbcca21 git checkout master hack && git commit -a then i expect the "reflog to be named" to follow *exactly these steps: master, build, master~1, dbcca21..., master, newmaster and _not_ just master~1m, dbcca21... cheers simon -- Serve - BSD +++ RENT this banner advert +++ ASCII Ribbon /"\ Work - Mac +++ space for low €€€ NOW!1 +++ Campaign \ / Party Enjoy Relax | http://dragonflybsd.org Against HTML \ Dude 2c 2 the max ! http://golden-apple.biz Mail + News / \
Attachment:
signature.asc
Description: OpenPGP digital signature