On 7/30/08, Dmitry Potapov <dpotapov@xxxxxxxxx> wrote: > On Wed, Jul 30, 2008 at 05:07:49PM -0400, Avery Pennarun wrote: > > FWIW, this problem would apply to any system that incrementally > > imports into git from another system using binary deltas. > > Not necessary. It depends on how import is done. You should not apply > this binary deltas to your working tree, but to files in the repo. And > obviously those files that are imported should be stored as is without > any conversion. In the same way as if you clone some git repo, you do > not apply any commit conversion to any existing commit. This conversion > should be done for *new* commits that you create locally. > > So, the problem with git-svn is mostly due to how the import is done. Of > course, the other part of that problem is that conversion setting in Git > and SVN for text files specified very differently. Hmm, if your first paragraphis true (do not apply any commit conversion to any existing commit), then in fact SVN's method for specifying text files doesn't really matter, right? It's just a bug in git-svn. Is it possible to have git-svn override core.autocrlf temporarily? If someone can give me a hint how to do that, I don't mind working up a patch for that. I can't see any situation where *not* doing so would even work (unless core.autocrlf=false already, of course). Have fun, Avery -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
