On 17/10/2014 21:52, Joe Taylor wrote: > Hi Bill, Hi Joe, > >>> Of course, a savvy user would edit the automatically generated message >>> so that "N8PR ZL/KE4PT" is sent. That's a legal message, because "ZL" >>> is one of the 339 "standard" prefixes defined in pfx.f90. They are >>> legitimate for the compound-callsign messages we call "Type 1" in the >>> WSJT-X User Guide. >> Oops, so my answer was partially incorrect and I should have suggested >> that as another alternative. >> >> Also that particular example response you give is valid as a free text >> message. > One might think so; but in fact it won't be encoded and sent as one. Nor > would the message "N8PR XL/KE4PT", which also has 13 characters. Try it > with jt65code or jt9code to see what happens. Hmm, serves me right for not testing it first.
So why doesn't it default to encoding as a free text message as a last resort? > > I agree that our repository could have a more logical layout. By all > means, let's arrange to build the common library with CMake. > > I had a brief try at using git-svn. I found it usable but not > immediately advantageous. Perhaps I would change my mind, in the > fullness of time. ;-) The advantages are more obvious coming from the standpoint of a regular git user, it doesn't give the full gamut of distributed source control capabilities but it does give most of the local features apart from non-linear branching, which is beyond being represented in Subversion. I would not give up being able to have multiple feature and bug fix branches on the go, being able to switch seamlessly between them and being able to commit to each of them incrementally as I make changes. Also I can choose to merge in public repository changes on a per branch basis to include others commits when I am ready to do integration testing. Then I can commit to svn all the committed changes along with their commit comments for each local feature or bugfix branch when I am ready to release to the World. Also the git stash stack is really handy for putting aside unfinished edits if I have to change focus to another feature for bugfix branch fro a short while. All this from one source tree and using one build tree (actually two, one Debug configuration and one Release configuration). Trying to do the above with Subversion requires many checkout trees and build trees and can be really tricky to keep track of without making mistakes. > > -- Joe > ------------------------------------------------------------------------------ Comprehensive Server Monitoring with Site24x7. Monitor 10 servers for $9/Month. Get alerted through email, SMS, voice calls or mobile push notifications. Take corrective actions from your mobile device. http://p.sf.net/sfu/Zoho _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
