|
| Re: Tracking of Audio Files [message #1008793 is a reply to message #1008771] |
Wed, 13 February 2013 21:29   |
 Robin Rosenberg
Messages: 332
Registered: July 2009 |
Senior Member |
|
|
Max Bedacht skrev 2013-02-13 21.32:
> I just started using eGit (I put one project under control). Prior to using eGit I was able to import and use audio files in this Java project. From the time of placing the
> project under eGit I am no longer able to effectively import audio files. The ones that were already in the project when it was put in Git still play, but any new ones
> imported show a question mark in the lower right corner of their icon and will not play. (The older ones have something that is yellow, but otherwise unrecognizable in the
> lower right corner.)
>
> Are there any restrictions or special handling required for tracked files under Git (or eGit)? Should I not track these files?
>
> Any help would be greatly appreciated.
I assume you are on Windows where autocrlf is the default if you have Git installed. The autocrlf feature will try to
autodetect binary files, but it only works if there is a nul byte wiithin the first 8Kib bytes of the file. You can
turn autocrlf off by setting the core.autocrlf config variable to false locally.
The core.safecrlf or gitattributes that would improve the situtation are not implemented yet. safecrlf is in gerrit, but
nobody seems to care :(, so I've left it until gitattributes supoort appears, which is supposed to come soon, but it
appears there is some delay.
Eclipse allows you to set the workspace to use LF only, even on Windows so you should be able to do cross-platform
work even on Windows without enabling autocrlf. If it is a pure Windows-project you can also disable autocrlf, which
is what I do.
-- robin
|
|
|
|
Powered by
FUDForum. Page generated in 0.01929 seconds
Search
Help
Register
Login
Home
