bookmark set: fast-forward onto a change built on the bookmark's newest head issue #78
closed: completed andymccall opened this · 0 comments
andymccall
From ~/oxygen_feedback.md issue #37 (vampirekiller, 2026-10-06): moving death-40 onto 1f9c9e79, a commit on top of it, was refused ('would lose 2 changes'): the two were early independent changes (issue #1, issue #7) every bookmark carries as extra heads, which 1f9c9e79 does not depend on. When the new heads hold the bookmark's newest head, keep those changes (as --upto) and say so. bookmark show (oxygen#73) explains extra heads.
From ~/oxygen_feedback.md issue #37 (vampirekiller, 2026-10-06): moving death-40 onto 1f9c9e79, a commit on top of it, was refused ('would lose 2 changes'): the two were early independent changes (issue #1, issue #7) every bookmark carries as extra heads, which 1f9c9e79 does not depend on. When the new heads hold the bookmark's newest head, keep those changes (as --upto) and say so. bookmark show (oxygen#73) explains extra heads.