I'd really like to completely turn this feature off (configurable before cloning the SVN repo), and it should be off by default until these problems are fixed, I think. gitattributes file to SVN.Ĭonsidering these kinds of problems (especially #2), it would be much better to have no. gitattributes set to false: You can't push a changed. gitattributes to the SVN repo via SVN and then pull via SmartGit. gitattributes set to false) There's an internal error if you add.
SMARTGIT COULD NOT CONNECT TO THE REPOSITORY WINDOWS
Note that due to the conversion you'll always have Windows EOL files in your worktree, even for files that have Unix endings in SVN, adding to the confusion. This also causes problems if you try to merge moved files on different branches (you have to ignore EOLs when merging). But if you move them, they are saved as Unix EOL files, and will be pushed to SVN with LF endings. If you modify them, they stay like that since Git doesn't convert existing CRLF EOLs to LF. Files in SVN with Windows EOLs are inserted into the Git repo as Windows EOLs.gitattributes entries, which will cause the folders in SVN to be deleted as well. You have to manually delete the leftover. gitattributes entries are still "propagated" as well: New folders with the same names as the previous files are created.
![smartgit could not connect to the repository smartgit could not connect to the repository](https://taiphanmempc.net/wp-content/uploads/2017/07/sua-loi-could-not-connect-to-repository-tren-kodi.jpg)
If you push to SVN, the files are moved, but the. gitattributes entries of the files remain.
![smartgit could not connect to the repository smartgit could not connect to the repository](http://vcloud-lab.com/files/packed/1wefanscc25vyhb8pjhafy2ydp8hzqvz6115zh72s851vakce3vxixbl1f58q9uhvsevl36f774cg0ackjx5d8awxsrid0zw668xrr5mxtp12hp11fxbus18vx0n1bndqjwiz4qnprsfj6htm5w5nnl5oguj460t.png)
![smartgit could not connect to the repository smartgit could not connect to the repository](https://user-images.githubusercontent.com/8424643/125558284-51cfe988-3a55-476f-bd95-8046d739b0a4.png)
If you delete or move files within the Git repo.gitattributes processing (tested with version 6.5.x, SVN integration mode "normal"): There are a few problems with the SVN integration related to.