hi all, is it possible that the pre-commit hook had changed recently? not sure if this was intended, but it currently breaks the use of git-svn, which imo is a huge inconvenience: -- tim@moka-mac:~/Documents/boost-trunk-git/boost$ git svn dcommit Committing to https://svn.boost.org/svn/boost/trunk ... A boost/sync/detail/generic/event_cv_emulation.hpp A boost/sync/detail/windows/event.hpp A boost/sync/event.hpp A libs/sync/test/event_test.cpp ERROR from SVN: A repository hook failed: Commit blocked by pre-commit hook (exit code 1) with output: /home/subversion/boost/hooks/check-mime-type.pl: trunk/boost/sync/detail/generic/event_cv_emulation.hpp : svn:mime-type is not set trunk/boost/sync/detail/windows/event.hpp : svn:mime-type is not set trunk/boost/sync/event.hpp : svn:mime-type is not set trunk/libs/sync/test/event_test.cpp : svn:mime-type is not set Every added file must have the svn:mime-type property set. In addition text files must have the svn:eol-style property set. For binary files try running svn propset svn:mime-type application/octet-stream path/of/file For text files try svn propset svn:mime-type text/plain path/of/file svn propset svn:eol-style native path/of/file You may want to consider uncommenting the auto-props section in your ~/.subversion/config file. Read the Subversion book (http://svnbook.red-bean.com/), Chapter 7, Properties section, Automatic Property Setting subsection for more help. Also, see http://svn.boost.org/trac/boost/wiki/BoostSubversion W: b7ab541813d43b7d74b44f57eb04c2625ce305a7 and refs/remotes/git-svn differ, using rebase: :040000 040000 4b2ab78eaa8f1e5fa80761a327da5066ca15d465 73aa096ac4b16618132d6d012e964b1790542c8f M boost :040000 040000 6146f06c45f590b38f76d123656cea13f24471d1 7a95e843ffc2f67fff874b6bd6c142b040423414 M libs Current branch master is up to date. ERROR: Not all changes have been committed into SVN, however the committed ones (if any) seem to be successfully integrated into the working tree. Please see the above messages for details. -- this used to work fine just a few days ago. was this done intentionally? if so, an announcement on the list with a comment on the implications for the git-svn users would have been good to see. best, tim