3 ms·
As expected, I see comments here like "Avoiding sh overcomplicates this." It's true. I found the shell-avoiding instructions no better, and possibly worse, than
by Zigurd 2y ago
As expected, I see comments here like "Avoiding sh overcomplicates this." It's true. I found the shell-avoiding instructions no better, and possibly worse, than shell commands.
But: what's sauce for the end user goose is sauce for the developer gander. Developers are users. Give developers good visual tools. Sadly I don't think there is a visual front end to git,, for example, that is any good among the handful I have tried and the dozens that attempt to make git safe, discoverable, and visually obvious.
- mplanchard 2y agoWish there was something like magit outside of emacs that I could recommend to people.
- 3np 2y agotig?
- progmetaldev 2y agoThis may be a backwards way to go about it, especially with an end goal of learning Git, but I feel that having learned Mercurial first helped me to more easily move to Git. Ultimately, it was using BitBucket's Mercurial repositories, and then Atlassian stating they were discontinuing Mercurial that forced me to jump to Git. Wanting to keep my Mercurial history forced me to learn parts of Git that I otherwise probably never would have touched. It seems Git has (at least for the present and near future) won the SCM wars for popularity. Working with mostly front end developers unfamiliar with code tools made me the go to guy at work, so I had no choice but to learn as much as I could about handling conflicts, as well as things most people rarely think about like a project's .gitignore and .gitattributes