Git's CLI is it's greatest weakness. Someone should really just scrap that part and rebuild it from scratch on sane ground.
You mean like: https://gitless.com
Learn the workings of Git, not just the commands (2015)
11–20 of 98 posts
Re: Learn the workings of Git, not just the commands (2015)
#12Git's CLI is it's greatest weakness. Someone should really just scrap that part and rebuild it from scratch on sane ground.
Poe's Law is getting me on your comment. If it wasn't sarcasm, what's an example of a weakness? IMHO, there's a learning curve to using git and especially getting to the point where you can be your team's go-to person for git questions. However, I hold the opinion that of the many technologies out there, git is among those that is worth any investment you can make in learning it. Personally, long term use of git has affected the way I code to bring more intention and organization to what I'm doing.
Re: Learn the workings of Git, not just the commands (2015)
#13Git's CLI is it's greatest weakness. Someone should really just scrap that part and rebuild it from scratch on sane ground.
Poe's Law is getting me on your comment. If it wasn't sarcasm, what's an example of a weakness? IMHO, there's a learning curve to using git and especially getting to the point where you can be your team's go-to person for git questions. However, I hold the opinion that of the many technologies out there, git is among those that is worth any investment you can make in learning it. Personally, long term use of git has…
quick: explain to me the difference between "git reset", "git revert" and "git restore", without looking up the docs.
Re: Learn the workings of Git, not just the commands (2015)
#14Earlier quoted context omitted.
Poe's Law is getting me on your comment. If it wasn't sarcasm, what's an example of a weakness? IMHO, there's a learning curve to using git and especially getting to the point where you can be your team's go-to person for git questions. However, I hold the opinion that of the many technologies out there, git is among those that is worth any investment you can make in learning it. Personally, long term use of git has…
quick: explain to me the difference between "git reset", "git revert" and "git restore", without looking up the docs.
But are these things a normal user would need to care about?
I bet if you created a great git desktop app with outstanding UI it would still have a few corners 99% of users would never touch or understand.
Re: Learn the workings of Git, not just the commands (2015)
#15"In this case, the conflicting result is left in the working directory for the user to fix and commit, or to abort the merge with git merge –abort."
I've used git for many years, and I still zip the repo folder, before doing a large merge, since 'fix the commit' can be a large effort with conflicts. Quickly renaming the repo root folder, then unzipping the old version can be quicker/safer, if you are not a git ninja and don't want to loose any work. There is probably proper command for it, but I sometimes get into a git mess that I cannot get out of. (reading stack overflow, trying get reset, git checkout, git reset --hard and so on)
Re: Learn the workings of Git, not just the commands (2015)
#16It's been over a decade and I still find this joke amusing: > @wilshipley git gets easier once you get the basic idea that branches are homeomorphic endofunctors mapping submanifolds of a Hilbert space. * https://twitter.com/agnoster/status/44636629423497217 (It's a 'spoof' on the Monad joke.)
Why does any post discussing _any_ aspect of git always results in these type of comments? "git is complex", "git command line is confusing me", "life would be easier is we all used subversion".
Please let us discuss git in peace.
(Although I admit that this one was funny)
Re: Learn the workings of Git, not just the commands (2015)
#17"In this case, the conflicting result is left in the working directory for the user to fix and commit, or to abort the merge with git merge –abort." I've used git for many years, and I still zip the repo folder, before doing a large merge, since 'fix the commit' can be a large effort with conflicts. Quickly renaming the repo root folder, then unzipping the old version can be quicker/safer, if you are not a git ninja…
"Zipping the folder" and keeping a copy of it is literally the sole purpose of a version control system. These kind of comments baffle me, quite honestly. But that is my fault, not yours.
Could you tell me what you think git is for and why you use it?
Re: Learn the workings of Git, not just the commands (2015)
#18Earlier quoted context omitted.
quick: explain to me the difference between "git reset", "git revert" and "git restore", without looking up the docs.
But are these things a normal user would need to care about? I bet if you created a great git desktop app with outstanding UI it would still have a few corners 99% of users would never touch or understand.
How to undo a change or revert to a previous version? That sounds like a pretty fundamental thing that a user would need to do, yes.
Re: Learn the workings of Git, not just the commands (2015)
#19"In this case, the conflicting result is left in the working directory for the user to fix and commit, or to abort the merge with git merge –abort." I've used git for many years, and I still zip the repo folder, before doing a large merge, since 'fix the commit' can be a large effort with conflicts. Quickly renaming the repo root folder, then unzipping the old version can be quicker/safer, if you are not a git ninja…
"Zipping the folder" and keeping a copy of it is literally the sole purpose of a version control system. These kind of comments baffle me, quite honestly. But that is my fault, not yours. Could you tell me what you think git is for and why you use it?
Congrats never getting into a time consuming git mess, but I do sometimes. This is a very rare event. Recently I tried changing the committers email (each commit has a name and email attached) but that commit was already pushed into the repo, and I could not recover from the resulting mess. Even had to delete my github fork, and fork again. Happens about twice a year, while I used git commits many times every day.
Re: Learn the workings of Git, not just the commands (2015)
#20In my experience it is fine to first learn only some required commands. One will run into cases, where ones understanding or imagination of how git works will not work any longer. In such cases one can still read up on how it works and build a new working understanding. Only important to not always just shrug, delete the repo and clone again. That will not really facilitate learning. Of course no one is stopping anyo…
I'm new to git. For now I use it from VSC, but I should probably give CLI a chance.
I must admit that I'm at the point where I shrug, delete and clone the repo if I'm stuck. Some errors and messages were to cryptic to me.