Thus people who have updated/fetched VAM from approx 2015-02-11 to 2015-02-15 may see "forced update" in git pull logs or get some strange merge history. The "wrong" master (98b714406d) which was available doesn't do any harm, it just dropped some of more recent commits and contained https://github.com/MarcWeber/vim-addon-manager/pull/164 which doesn't really affect VAM's behaviour. If you ran into this "issue" you can git reset --hard origin/master to continue following current upstream.
How long to keep this? I'd say at least 3 month. Should this even be moved into README? I'm unsure. Let us know, please!
ZyX-I
commented
9 years ago
Thus people who have updated/fetched VAM from approx 2015-02-11 to 2015-02-15 may see "forced update" in git pull logs or get some strange merge history. The "wrong" master (98b714406d) which was available doesn't do any harm, it just dropped some of more recent commits and contained https://github.com/MarcWeber/vim-addon-manager/pull/164 which doesn't really affect VAM's behaviour. If you ran into this "issue" you can git reset --hard origin/master to continue following current upstream.
How long to keep this? I'd say at least 3 month. Should this even be moved into README? I'm unsure. Let us know, please!