Viewing profile — lennartregebro

And that simile also has nothing to do with what happened. First of all, this is not a matter of me doing something wrong because I didn't learn enough of gits internals or didn't …

To be honest, none of the issues I've seen are in any way dependent on workflow. That pull and push by default work on different branches is not a matter of workflow, it's a confus…

That's interesting, and maybe I'll try that in the future. But just as with the "matching" vs "current" why is the default here the thing that is guaranteed to cause problems, inst…

Sure, which is why I made a backup first. I didn't lose any data. I'm just ranting about what is some of the bad things with git.

No, git is not hard because it's powerful. It's hard because it's defaults are non-sensical, and it's user interface are neither close enough to how it's internal mechanics to be p…

It's nice to know things have improved. Apparently they will also remove the stupid "matching" default on push in version 2. But I think that pull and push still will not do exactl…

Sure, that's OK. But shouldn't that command be explicit ?

You are of course correct. However on Gits' homepage: "Git is a free and open source distributed version control system".

No the message is rather: "If you press this button, the engine will vanish", and when you then look under the hood, it turns out the car never had an engine, it was a little dwarf…

A revision control system that can lose history is a fundamentally flawed revision control system. (Note that lose history is not the same as explicitly delete certain revisions). …