Software Crafting
  • Introduction
  • Tools
    • *nix\/Shell Setup
      • zsh
        • Switching to zsh
        • zsh Themes
        • zsh Prompt Escape Sequences
        • Troubleshooting
    • git
      • Addressing common errors
    • GitHub
      • GitHub Markdown Cheetsheet
      • Configure \/ Make \/ Make Install
    • tmux
      • Useful tmux Links
    • vim
      • Build from Repository Tips
    • Ubuntu
    • Misc
  • Seminars
    • 2018 SCaLE 16x Container Days
    • 2017 MATLAB Expo
    • 2017 SoCal Code Camp
    • 2017 SCNA
    • 2017 MathWorks Advisory Board
      • Day 1: MATLAB Platform and Data Analytics
      • Day 2: Model-Based Design with Simulink: Modeling and Simulation
      • Day 3: Model-Based Design with Simulink: Code Gen and V&V
    • Agile Systems Engineering Planning Using Six Thinking Hats
    • 2016 SoCal Code Camp
    • 2016 SCNA
    • 2016 Pre-SCNA Workshop
  • Programming
    • Javascript
      • Node.js
        • Frameworks
    • Python 2
    • Rust
    • Makefiles
    • GNU General Public License (GPL)
  • Crafting
  • Algorithms
  • Amazon Web Services
    • Administrating
Powered by GitBook
On this page
  • Windows file ending (crlf) and Unix file ending (lf) incompatibilty
  • Upgrade to macOS breaks git
  • References

Was this helpful?

  1. Tools
  2. git

Addressing common errors

PreviousgitNextGitHub

Last updated 6 years ago

Was this helpful?

Windows file ending (crlf) and Unix file ending (lf) incompatibilty

git config --global core.eol lf
git config --global core.autocrlf input
git rm -rf --cached .
git reset --hard HEAD

Upgrade to macOS breaks git

On macOS, git is attached to XCode’s command line tools. It needs to be updated whenever macOS is upgraded.

xcode-select --install

References

Parse errors due to ^M end of line
How do I force git to use LF instead of CR+LF under windows?
xcrun: error: invalid active developer path (/Library/Developer/CommandLineTools), missing xcrun