Hi Bill, I'm not certain as to how other developers manage their commits, but, I typically run a separate checkout using svn://<url> when using SVN that adds the developer username to the url. Before running separate checkouts, I just committed from the src directory using my SF credentials.
Joe may be able to shed a bit more light on this than I can, as outside of a very few commits, I've not made many commits to the WSJT-X branch. 73's Greg, KI7MT On 3/2/2017 11:35 AM, Bill Somerville wrote: > On 02/03/2017 18:04, Greg Beam wrote: >> If users want to test svn:// v.s.http://, they can edit the top of: > > Hi Greg, > > thanks for filling the details for the JTSDK Subversion URLs. Since > SourceForge no longer advertise Subversion access via HTTP I would > suggest we either use an HTTPS or SVN scheme. Subversion on Windows > ships with its own SSL libraries so there should be no issue with SSL > being installed when using HTTPS. > > I use SSH+SVN all the time on SourceForge and have no issues with it but > that is for read+write access hence the SSH wrapper. > > Interesting that no one has commented on how they get read+write access, > does anyone do that with the JTSDK? > > 73 > Bill > G4WJS. > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > wsjt-devel mailing list > wsjt-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/wsjt-devel > ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
