FredS

By default after a clone you should have the source of your clone set as 'origin'. more: https://stackoverflow.com/questions/2883840/differences-between-git-pull-origin-master-git-pull-origin-master#2883857 Although I do use Bash, I find TortoiseGit much easier and for that its r-click>Pull 🙂

Once you have a git repo all you need is Pull: https://git-scm.com/docs/git-pull

RSP-14289 is still open and a comment suggests it still plays this way in Rio.. Created: 24/Apr/16 4:05 PM

The coveted Enterprise sector will just love this..

No argument there, but at least you can 'unregister' and move without problems, if you crash you can get it up for a fixed fee. Checking this ability in the Delphi License Manager this morning showed the mess that is, plus I didn't see a place where it shows how many activations you have left either which means that the only time you find that out is after digging yourself out of a crash situation.

Got that confused with IBExpert which has that feature and a fixed price for reactivation after your subscription elapses..

Not sure, thought that exists.. However there is no way to deactivate after a crash. Either way, what you owned yesterday is today only a rental.. and at the mercy of a 'rude' renewal department at that..

To me it sounded like 'the litigation department is bored'..

From the GM: New Updates and Changes to the Registration “Bumps” Policy " We updated our processes and now route all issues raised from users who are not on Update Subscription to Sales and Renewals. "

I often wonder how many issues in a mature product are actually the misuse of Version Control..

It appears that feature is no longer implemented..

Tasks can stay idle for something like 5 minutes and then longer in the retired state.

Not an issue, as I said before 99.9% of the time recompiling fixes it. For the remainder, commenting out a line , any line, do a build all then uncommenting the same line will fix it..

Yeah, except yesterday I tried to compile that project via msbuild and it still generated the same error:

RSP-11530 was fixed for Rio, which means it should also show the correct Build.

Yes, one of the first things I did back in XE7. However Writeln(TOSVersion.ToString); returns: Windows 10 (Version 10.0, Build 0, 64-bit Edition) Because in in TOSVersion.Create: if not GetNetWkstaMajorMinor(MajorNum, MinorNum) then GetProductVersion(kernelbase, MajorNum, MinorNum, BuildNum); The call to GetNetWkstaMajorMinor doesn't return a Build, if it failed GetProductVersion would have returned the correct Build.

OK but.. it reports compatibility which may be important to know.. Of course TOSVersion has always reported the correct version, blatantly ignoring any attempt by M$ to lie 🙂

It may be time to focus on the positive news, three new skins have been released since Rio. Just waiting for all Development Managers to each write a blog about this exciting new feature 🙂

There is a benefit in maintaining your own fork, wish it was simpler to find the most up to date fork though and fork that 🙂 Also generating a branch before a making a pull request isn't a big deal as long as one knows about that..

Didn't know that, here is a way to do that within GitHub

I was adding something to a tested function and the only way I could justify not retesting all of it is by using 'goto'..

Used my first 'goto' a couple of weeks ago 🙂

Check, so the free tool can downshift to accommodate Delphi 🙂 http://wiki.freepascal.org/Helper_types#record_helper

Stefan's link shows 75 bugs.. then there are those 'secret' internal ones..

Those are two different things, but using your release to beta test your tool set isn't really for everyone..