Closed bictorv closed 2 years ago
Sigh. syshst;hosts3 is too clever for its own good, and rejects two hosts with the same address. I'll try to uncommit the second commit.
Depending on your branching model, you might typically remove the latest commit by doing git reset --hard HEAD~
rather than revert. I did this now and force pushed the branch.
Thanks! While I have a "pro" account, I'm not really a git pro. ;-)
The first commit is ok, but the second results in this:
This typically happens when there's something wrong with the host table. Maybe if you run
:syshst;hosts3
manually with the updated table, it will tell you if there's something it doesn't like.