msysgit | 易学教程

Git Bash is extremely slow on Windows 7 x64

阅读更多关于 Git Bash is extremely slow on Windows 7 x64

问题 I\'ve been using Git on both Windows and Ubuntu during the development of a small project, frequently flipping back and forth between the two. The issue is that Git Bash consistently becomes slow. When I say slow, I mean that running cd takes anywhere from 8-25 seconds, running git commands take from 5-20 seconds, and ls can take up to 30 seconds sometimes. Needless to say, this is not fun, not to mention unproductive. I know Git is slower on Windows, but this is ridiculous. The one solution

How do I force git to use LF instead of CR+LF under windows?

阅读更多关于 How do I force git to use LF instead of CR+LF under windows?

问题 I want to force git to checkout files under Windows using just LF not CR+LF . I checked the two configuration options but I was not able to find the right combination of settings. I want it to convert all files to LF and keep the LF on the files. Remark: I used autocrlf = input but this just repairs the files when you commit them. I want to force it to get them using LF . Probably I wasn\'t so clear: the repository is already using LF but the files checked out using msysgit are using CR+LF

git, msysgit, accents, utf-8, the definitive answers

阅读更多关于 git, msysgit, accents, utf-8, the definitive answers

问题 I\'ve read in some places that there are problems with git (or just msysgit?) and character encoding - I believe it\'s only a problem in file names. What I\'d like is some \'definitive\' (or at least authoritative) information about: What exactly are the \'problems\'? (The symptoms) What are the causes? (Briefly) In what scenarios is this a show stopper? Is there any resolution in sight, or failing that any workarounds? I hope this question isn\'t too vague, I think it would be good to have

Git 1.6.4 beta on Windows (msysgit) - Unix or DOS line termination

阅读更多关于 Git 1.6.4 beta on Windows (msysgit) - Unix or DOS line termination

问题 I am installing msysgit 1.6.4 beta on my Win Vista development VPC. An install screen is requesting whether I want to use Unix line termination or DOS line termination. Ordinarily, I\'d choose DOS, but the setup text indicates that DOS termination may mean files do not work with all of Git\'s command line tools. The Unix line termination states \"...most [Windows] applications can handle this...\". Does anyone know which option I should choose to use Git via the shell for my VS 2008 work? 回答1

Trying to fix line-endings with git filter-branch, but having no luck

阅读更多关于 Trying to fix line-endings with git filter-branch, but having no luck

问题 I have been bitten by the Windows/Linux line-ending issue with git. It seems, via GitHub, MSysGit, and other sources, that the best solution is to have your local repos set to use linux-style line endings, but set core.autocrlf to true . Unfortunately, I didn\'t do this early enough, so now every time I pull changes the line endings are borked. I thought I had found an answer here but I can\'t get it to work for me. My Linux command line knowledge is limited at best, so i am not even sure

fatal: early EOF fatal: index-pack failed

阅读更多关于 fatal: early EOF fatal: index-pack failed

问题 I have googled and found many solutions but none work for me. I am trying to clone from one machine by connecting to the remote server which is in the LAN network. Running this command from another machine cause error. But running the SAME clone command using git://192.168.8.5 ... at the server it\'s okay and successful. Any ideas ? user@USER ~ $ git clone -v git://192.168.8.5/butterfly025.git Cloning into \'butterfly025\'... remote: Counting objects: 4846, done. remote: Compressing objects:

How to change line-ending settings

阅读更多关于 How to change line-ending settings

Is there a file or menu that will let me change the settings on how to deal with line endings? There are 3 options: Checkout Windows-style, commit Unix-style Git will convert LF to CRLF when checking out text files. When committing text files, CRLF will be converted to LF. For cross-platform projects, this is the recommended setting on Windows ("core.autocrlf" is set to "true") Checkout as-is, commit Unix-style Git will not perform any conversion when checking out text files. When committing text files, CRLF will be converted to LF. For cross-platform projects this is the recommended setting

Ignoring directories in Git repos on Windows

阅读更多关于 Ignoring directories in Git repos on Windows

How can I ignore directories or folders in Git using msysgit on Windows? stew Create a file named .gitignore in your project's directory. Ignore directories by entering the directory name into the file (with a slash appended): dir_to_ignore/ More info here . brainwavedave By default windows explorer will display .gitignore when in-fact the file name is .gitignore.txt Git will not use .gitignore.txt And you can't rename the file to .gitignore because explorer thinks its a file of type gitignore with no name. Non command line solution: You can rename a file to ".gitignore." and it will create "

Where do the settings in my Git configuration come from?

阅读更多关于 Where do the settings in my Git configuration come from?

I've noticed that I have 2 listings for core.autocrlf when I run git config -l $ git config -l core.symlinks=false core.autocrlf=false color.diff=auto color.status=auto color.branch=auto color.interactive=true pack.packsizelimit=2g help.format=html http.sslcainfo=/bin/curl-ca-bundle.crt sendemail.smtpserver=/bin/msmtp.exe diff.astextplain.textconv=astextplain rebase.autosquash=true user.name=name user.email=email@example.com core.autocrlf=true Those last 3 (from user.name down) are the only ones in my c:\users\username\.gitconfig file. Where are all of the other ones coming from? Why is core