Follow-up Comment #26, bug #58736 (project groff):
[comment #25 comment #25:] > [comment #24 comment #24:] > > commit 0f3c777f5dbfc5dc1f4668cfd8b8fd35bb818623 > > Author: G. Branden Robinson <[email protected]> > > Date: Thu Dec 16 19:00:55 2021 +1100 > > > > tmac/tmac.am: Mark a test as XFAIL. > > Actually commit ca654b167ea9518366ba00fc40e5359a8ddb90c5 <http://git.savannah.gnu.org/cgit/groff.git/commit/?id=ca654b167ea9518366ba00fc40e5359a8ddb90c5>. No such commit as the ID cited above. > > > commit 21e6881d585902f711464c413681c7c56ac35bd1 > > Author: G. Branden Robinson <[email protected]> > > Date: Thu Dec 16 18:54:01 2021 +1100 > > > > Revert "[me]: Fix Savannah #58736." > > Actually commit 757ea37560caf6deac85ac936496e918b3166c3d <http://git.savannah.gnu.org/cgit/groff.git/commit/?id=757ea37560caf6deac85ac936496e918b3166c3d>. Branden is clearly reporting from a parallel universe. Whoops. Sorry, I must have done this from a working tree before I pushed. I normally don't update Savannah tickets with resolver messages until I have pushed a batch of commits. I guess my workflow got thrown off because I wasn't updating with a "resolver" this time. These bogus IDs are the result of the nonstop orgy of rebases that my working tree sees, and of which precious little evidence escapes. Until recently, it seems. I'll try to be more careful. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?58736> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
