Linus Torvalds - that commit is not mine
Linus Torvalds - that commit is not mine
You're viewing a single thread.
12 comments
-
Short TL;DR: nothing burger
Longer TL;DR: Linus sees bad changes to the git tree by Kees Cook that he interprets as being of human origin and intentional, calls them "malicious" changes and orders that Kees Cook's privileges be revoked. Turns out that the "git-filter-repo" tool being used was actually the culprit as it is very powerful and incorrect usage explains the changes. Discussion then moves toward implementing safety checks in the tooling. Kees gets his permissions back.
-
Cook's razor: "Never attribute to malice that which is adequately explained by screwing up
gitcommands."-
The person who created
gitclearly cannot be trusted to write good kernel code. I'm CC'ing Konstantin to disable his account, whoever he is.-
git-filter-reposeems to be separate fromgit
-
-
screwing up git commands
You mean "using git." It's the only piece of software that I hate with Oracle. Jujutsu is a breath of fresh air and I can ignore that git ever existed.
-
git is genuinely one of the best tools ever created. It is an extremely simple idea with crazy effectiveness and a reasonable UX that is a bit off putting at first but makes a lot of sense later on.
That said, I'd genuinely be curious what you think jj has improved upon git.
-
The command line of jj makes sense and is easy to understand. I have to use graphical git clients because I want to cry every time I have to use its CLI.
-
That's interesting; I find the git CLI pretty intuitive especially for basic use cases most people would need, but I've also used git for 15 years now.
-
I have only been using it for ~ 4 years and the UX seems pretty logical even for not-basic cases.
Maybe because it was only my second VCS^[the first one being folders with timestamps], it didn't seem at all problematic to me. On the contrary, every time, I just found myself going "nice", whenever I found a new feature.
When it comes to
git restore ., well, you won't userm -rf *in your working directory, right?I haven't used
gitbased GUIs much. Some of the functions that my IDE provides, I use now and then. Being able to see thegit blamefor a file, right in place, scrolled to the same line as I was looking at the code, helps quite a bit (and so does the git based annotations).
But for things likecommit,restore,pull,push,rebaseand things that will write something, I just use the CLI, because I feel like I know what is going to happen ad that gives me confidence. -
I find the git CLI pretty intuitive
You might be the first person to ever say that! How do I delete a remote branch?
-
-
-
-
-
-
12 comments