Package: git-debrebase Version: 6.2 Usertags: rsn If you run vanilla git rebase, and go back too far, git rebase can destroy important commits such as the anchor or last pseudomerge. It will tend to do this even if you don't actually modify the todo file.
The documentation should have stronger warnings about this. Perhaps: - In git-debrebase(5), after LEGAL OPERATIONS, add a new (sub)section ILLEGAL OPERATIONS which specifically mentions git-rebase starting before the most recent nonlinear commit; and general merges. - In git-debrebase(1), at the end of the first usage mode (a vanilla debrebase), a note that it is hazardous to use plain git-rebase on git-debrebase branches, and a cross-reference to the above. - Perhaps expand on or strengthen the "too early" warning in dgit-maint-debrebase. Ian. -- Ian Jackson <ijack...@chiark.greenend.org.uk> These opinions are my own. If I emailed you from an address @fyvzl.net or @evade.org.uk, that is a private address which bypasses my fierce spamfilter.
