This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| troubleshooting [2025/05/25 15:21] – admin | troubleshooting [2025/06/07 19:56] (current) – admin | ||
|---|---|---|---|
| Line 4: | Line 4: | ||
| **Git functionality**\\ | **Git functionality**\\ | ||
| - | We have simplified Git to such an extent that we have only given a small subset of all the stuff that //Git// can do. If you encounter some unusual situations in //Git//, you can always right-click on the folder for the pop-up menu, and drop down to the CMD window of that folder, and execute //Git// commands manually there. In many cases you can also use the excellent // | + | We have simplified Git to such an extent that we have only given a small subset of all the stuff that //Git// can do. If you encounter some unusual situations in //Git//, you can always right-click on the folder for the pop-up menu, and drop down to the CMD window of that folder, and execute //Git// commands manually there. In many cases you can also use the excellent // |
| **Handling known_hosts file**\\ | **Handling known_hosts file**\\ | ||
| Line 14: | Line 14: | ||
| + | **Known Issues**\\ | ||
| + | //Git Winch// works closely with the underlying Windows Operating system. Once you start //Git Winch// and then you start making changes to the work folder and/or sub-folders underneath the work folder, Git Winch will throw some errors and you may get some technical messages. Usually //Git Winch// will not work properly after that. So if you do want to make any changes to those folders, do all that when //Git Winch// is NOT running. | ||
| ----- | ----- | ||
| [[/ | [[/ | ||