Fix cvsexportcommit with CR/LF line endings
#132
Conversation
When using cvsnt + msys + git, it seems like the output of cvs status had \r\n in it, and caused the command to fail. This fixes that. Signed-off-by: Dustin Spicuzza <[email protected]> Signed-off-by: Johannes Schindelin <[email protected]>
dscho
force-pushed
the
cvsexportcommit-crlf
branch
from
74ad982 to
9b508af
Compare
|
/submit |
|
Submitted as [email protected] |
![gitgitgadget[bot]](https://avatars.githubusercontent.com/in/12836?s=60&v=4){kind=small}
|
This branch is now known as |
|
This patch series was integrated into pu via git@7ac9d1f. |
|
This patch series was integrated into pu via git@8deb8fe. |
|
This patch series was integrated into pu via git@3a51cf0. |
|
This patch series was integrated into pu via git@ae02f76. |
|
This patch series was integrated into pu via git@e5d7ff8. |
|
This patch series was integrated into pu via git@2ce2dbc. |
|
This patch series was integrated into pu via git@c36d835. |
|
This patch series was integrated into pu via git@f3cc608. |
|
This patch series was integrated into next via git@9874698. |
|
This patch series was integrated into pu via git@8c06492. |
|
This patch series was integrated into pu via git@b5fb62b. |
|
This patch series was integrated into next via git@b5fb62b. |
|
This patch series was integrated into master via git@b5fb62b. |
|
Closed via b5fb62b. |
When using CVSNT, we need to be prepared to grok CVS output with CR/LF line endings.
While we do not use CVSNT in Git for Windows, this patch made its way into Git's source code via the Git for Windows project (probably because of the ease of GitHub PRs), and we had not a single complaint for over 2 years, so I would consider this patch ready to be included in core Git.