1 Git 中文教程
http://www.bitsun.com/documents/gittutorcn.htm
2 使用 Git 管理源代码
http://www.ibm.com/developerworks/cn/linux/l-git/index.html
3 Everyday GIT With 20 Commands Or So
http://www.kernel.org/pub/software/scm/git/docs/everyday.html
------------------------------------------------------------------------------------------------------------------------------------------
错误排除:
1 Git on Windows: “You have some suspicious patch lines”
If you are using Git under Windows using cygwin, and you got through the initial problems, you will soon realize that Git likes to fail with “You have some suspicious patch lines” when committing.
The cause for this problem is the carriage-return/line-feed problem of Git under Windows/cygwin: The patches contain a trailing line-feed if you edited them with a Windows editor and not strictly inside cygwin. This will trigger the pre-commit hook to fail on patches where the last line of a file has been changed.
To solve the problem, you need to edit .git/hooks/pre-commit and comment out the following lines:
if (//s$/) {
bad_line("trailing whitespace", $_);
}
Now committing should work.
or
Specifically, something like this should work:
if (s/^/+//) {
$lineno++;
s//r//g; # get rid of any carriage returns
chomp;
if (//s$/) {
bad_line(”trailing whitespace”, $_);
}
…
Setting $/ globally might screw up something else - so this is probably the better option.
http://www.bitsun.com/documents/gittutorcn.htm
2 使用 Git 管理源代码
http://www.ibm.com/developerworks/cn/linux/l-git/index.html
3 Everyday GIT With 20 Commands Or So
http://www.kernel.org/pub/software/scm/git/docs/everyday.html
------------------------------------------------------------------------------------------------------------------------------------------
错误排除:
1 Git on Windows: “You have some suspicious patch lines”
If you are using Git under Windows using cygwin, and you got through the initial problems, you will soon realize that Git likes to fail with “You have some suspicious patch lines” when committing.
The cause for this problem is the carriage-return/line-feed problem of Git under Windows/cygwin: The patches contain a trailing line-feed if you edited them with a Windows editor and not strictly inside cygwin. This will trigger the pre-commit hook to fail on patches where the last line of a file has been changed.
To solve the problem, you need to edit .git/hooks/pre-commit and comment out the following lines:
if (//s$/) {
bad_line("trailing whitespace", $_);
}
Now committing should work.
or
Specifically, something like this should work:
if (s/^/+//) {
$lineno++;
s//r//g; # get rid of any carriage returns
chomp;
if (//s$/) {
bad_line(”trailing whitespace”, $_);
}
…
Setting $/ globally might screw up something else - so this is probably the better option.