Earlier quoted context omitted.
I understand your sentiment but git is really not all that hard. And knowing a few things that go beyond bog-standard checkout/commit/push, especially history-rewriting activities, will greatly improve quality of commit-history - which might not be of much use for you but might help other engineers working on your project to make easier sense of what's going on. And on another note, git is probably one of the longer-…
I'd argue that CVS outlasted git by at least a couple of decades...
Git tips and tricks
141–143 of 143 posts
Re: Git tips and tricks
#142Earlier quoted context omitted.
Why even use git then? `scp code server:code` does what you need. This isn't a rhetorical question.
Because all the organizations that pay me to write code host their code centrally on GitHub
But then it's GitHub you need to know, not git.[1] And doesn't that have a point-and-clicky Web interface, like any "Upload files here!" Web site?[2]
[1]: Seems you're being fooled, by organisations that also believe it, that git is GitHub and/or vice versa.)
[2]:Sorry, I've had an account there since about forever, but hardly ever (never?) used it.
Re: Git tips and tricks
#143Earlier quoted context omitted.
Because all the organizations that pay me to write code host their code centrally on GitHub
> GitHub But then it's GitHub you need to know, not git.[1] And doesn't that have a point-and-clicky Web interface, like any "Upload files here!" Web site?[2] [1]: Seems you're being fooled, by organisations that also believe it, that git is GitHub and/or vice versa.) [2]:Sorry, I've had an account there since about forever, but hardly ever (never?) used it.