but it also means that the line endings might not be correct for the platform. In your example forcing Windows CRLF endings could cause issues in Linux and OSX.
A better suggestion is to normalize the files upon commit and checkout.
- Set your global core.autocrlf to input for linux/OSX or true for Windows
- Add "* text" in the .gitattributes file
When committed they are stored with LF, on checkout they are converted to the OS's native line endings.
For more about this, read https://help.github.com/articles/dealing-with-line-endings
It also has a tip on how to re-normalize the entire repo if you are ever in the situation again where the developers have been using different line endings.
Another great blog about line endings with git is http://timclem.wordpress.com/2012/03/01/mind-the-end-of-your-line/
When you create the Exception Breakpoint, by default it is created only for that project. (You can see part of the XCode project icon in the above screenshot)
Right click on the breakpoint and choose Move Breakpoint To > User. This will add it to your user profile which is applied to all projects. This way you don't need to remember to do it every time you open/create another project.
The Witgui site discusses this issue and has a couple of workarounds. Basically you need to chmod the /dev/disk of your WBFS drive so normal users can access it. This is either a per disk connect chmod call or permanent via a script called when the disk is mounted.
Password caching is already available (as of git 1.7.10) using the credential helper. It handles storing/retrieving your password from your OSX Keychain without having to do any of the sed or tr parsing you have posted here. You can learn how to set this up on the password-caching section of the GitHub help page at https://help.github.com/articles/set-up-git
Another option is to use the SSH URL instead of HTTPS.
https://help.github.com/articles/why-is-git-always-asking-for-my-password
If you set up SSH keys on your GitHub account, you won't have to bother with passwords at all.
Hope this helps
Achievements
29 Karma
973 Total ProTip Views
Raven
Nice to see others using 'sudo $(history -p !!)'. I've been using it for a while but with a slightly different alias name. :)
Reference: http://xkcd.com/149/