You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Obviously, the first pick was not included, by mistake.
So every time reset is executed, it should record the HEAD's hash in a growing list, and verify in the end that they are reachable (possibly using the refs/rewritten/* refs with name-rev to display nicer names).
This feature is similar in spirit to the warning when calling git checkout <branch> on a detached HEAD, where the user is told about the commits that would now be lost.
It is easy to do this:
Obviously, the first
pick
was not included, by mistake.So every time
reset
is executed, it should record the HEAD's hash in a growing list, and verify in the end that they are reachable (possibly using therefs/rewritten/*
refs withname-rev
to display nicer names).This feature is similar in spirit to the warning when calling
git checkout <branch>
on a detached HEAD, where the user is told about the commits that would now be lost.Migrated from https://bugs.chromium.org/p/git/issues/detail?id=32
The text was updated successfully, but these errors were encountered: