: As I understood this was an svn eol style problem. I provided a git diff patch. : Is it possible to avoid this svn problem in a git patch? : Could ant precommit catch this on a git branch? I did not use that this time.
i don't know if there is anything you can do when using git and generating a parth to avoid problems like this. When using "svn diff" it includes metdata like this in the diffs... --CUT-- Property changes on: foo/bar/baz.java ___________________________________________________________________ Added: svn:eol-style + native --CUT-- ...and suposedly if you use "svn patch" it will look for that extra data and apply those properties -- but i've never actually tried it. So i suppose if you cna make "git diff" tack on that same syntax, you've done everything you can do. But if the committer (like me) typically just uses the "patch" command, then that metadata is just going to be ignored. -- but "ant preocmmit" run just prior to commit will still catch this. -Hoss http://www.lucidworks.com/ --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
