Corupted git repository & git fsck needed ? about vim-mark HOT 2 CLOSED

For reference you can check
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=743227
or
https://groups.google.com/forum/#!topic/binary-transparency/f-BI4o8HZW0

from vim-mark.

a bit of history

The Mark plugin originally was created by another developer (up to version 1.1.8), outside of Git. There's a http://vim-scripts.org/ mirror that reads the released plugin versions from http://www.vim.org/ and commits them into a GitHub repository (for easier consumption with plugin managers). When I took over development, this also was done outside of Git. When I (recently) moved the plugin code to Git, I based my changes on that vimscripts fork (you'll notice that this repo is forked from vim-scripts/Mark).

analysis

Those invalid author/committer line - bad time zone commits are from the original vimscripts.org import. I don't think it's actual corruption of data, just some metadata that isn't in the format that Git expects.

Thank you for alerting me to the issue; it's a very interesting aspect of Git that I wasn't aware of so far (and I agree that it's a good practice to enable those fsck settings). However, I don't think there's much I can do to fix this, other that somehow rewriting the entire history, which probably has worse consequences than having to live with these very old invalid commits. I hope you agree.

from vim-mark.