Git Tutorial
Git Useful Resources
Selected Reading
- Git - Online Repositories
- Git - Different Platforms
- Git - Handling Conflicts
- Git - Managing Branches
- Git - Patch Operation
- Git - Tag Operation
- Git - Fix Mistakes
- Git - Delete Operation
- Git - Rename Operation
- Git - Move Operation
- Git - Stash Operation
- Git - Update Operation
- Git - Push Operation
- Git - Commit Changes
- Git - Review Changes
- Git - Perform Changes
- Git - Clone Operation
- Git - Create Operation
- Git - Life Cycle
- Git - Environment Setup
- Git - Basic Concepts
- Git - Home
Git Useful Resources
Selected Reading
- Who is Who
- Computer Glossary
- HR Interview Questions
- Effective Resume Writing
- Questions and Answers
- UPSC IAS Exams Notes
Git - Different Platforms
Git - Different Platforms
GNU/Linux and Mac OS uses pne-feed (LF), or new pne as pne ending character, while Windows uses pne-feed and carriage-return (LFCR) combination to represent the pne-ending character.
To avoid unnecessary commits because of these pne-ending differences, we have to configure the Git cpent to write the same pne ending to the Git repository.
For Windows system, we can configure the Git cpent to convert pne endings to CRLF format while checking out, and convert them back to LF format during the commit operation. The following settings will do the needful.
[tom@CentOS project]$ git config --global core.autocrlf true
For GNU/Linux or Mac OS, we can configure the Git cpent to convert pne endings from CRLF to LF while performing the checkout operation.
[tom@CentOS project]$ git config --global core.autocrlf inputAdvertisements