Nicolas Pitre <nico@xxxxxxx> writes:
> It's just that moving around amongst thousands of commits to pin point a
> particular commit might require some digging work. This is why there
> might be some value in a particular position and why there is an attempt
> at protecting that "work".
>
> But since moving to another position while still remaining detached from
> any branch has the same potential for losing the important position and
> so without any kind of protection then it makes no sense to have such a
> protection when moving back to a branch.
Thanks -- I'd agree.
Also I agree that "reflog on HEAD" is the right direction as it
makes these 'protection' unnecessary. I've applied all your
patches from today on the topic, along with Johannes's "log -g
@{now}".
-
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