1. If we don't care that checkouts from git of old revisions may have incorrect EOLs, we can commit a fix to all affected files in SVN HEAD to ensure their svn:eol-style exactly matches what https://svn.boost.org/trac/boost/wiki/BoostSubversion says it should be.
2. If we do care that checkouts from git any revision are always correct, we'll need to do some monkeypatching during the svn to git conversion process (i.e. check for incorrectness, and fix).
Niall
I prefer the first option, since it's not just a git problem and keeps the two repositories consistent.
Dave Abrahams and I have come to an agreement that fixing up all past git commits to be EOL correct is probably the one choice acceptable. We're currently working out the details off list.
Might also be a good idea to introduce some pre-commit SVN hooks to ensure appropriate line endings.
Boost already has those, but some incorrectness has slipped in over time. Niall --- Opinions expressed here are my own and do not necessarily represent those of BlackBerry Inc.