OS: Windows 7 x64 TortoiseSVN: 1.13.1 SVN: svn, version 1.13.0 (r1867053) compiled Oct 31 2019, 20:41:49 on x86-microsoft-windows
Preparations for the Sourceforge hub: 1. Install putty 2. Install ssh key to the Sourceforge 3. Run putty pageant and add the shh key Steps to repro: 1. Create `test_root` repo 2. Create `test_ext1` repo 3. Checkout all repos using `svn+ssh://<user>@svn.code.sf.net/p/<project>/...` url (`svn+ssh` protocol plus the user to avoid the TortoiseSvn for asking for the login user on update): <repo> -> <WC> `test_root` -> `test_root1` `test_root` -> `test_root2` `test_ext1` -> `test_ext1` 4. Make an external in the `test_root1` working copy to the `test_ext1` repo: `svn://svn.code.sf.net/p/<project>/test_ext1/ test_ext1` (`svn` protocol) 5. Commit `test_root1` working copy 6. Update `test_root2` working copy (all should be fine from here) 7. Change the external in the `test_root1` working copy to: `// svn.code.sf.net/p/<project>/test_ext1/ test_ext1` (remove the scheme part) 8. Commit `test_root1` working copy (don't update it) 9. Update `test_root2` working copy TortoisePlink will ask for the `login as` 4 times. 10. Update `test_root2` working copy again TortoisePlink will ask for the `login as` 1 time. In real project the step 9 loop can be really too long and only recheckout helps to reduce quantity of login asks. Of cause you can fix the keep asking by adding user name into all extenals urls, but that is a bad practice. -- You received this message because you are subscribed to the Google Groups "TortoiseSVN" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tortoisesvn/581465c4-773b-49fe-8fd4-edaf725e874b%40googlegroups.com.
