311–318 of 318 posts
Hey all--if you find things wrong, post 'em. I'll clean 'em up. :) Love, Beej
There's an issue for the IPC guide on GitHub that's almost a year old with zero reaction.
I've fixed it, and wrote a quick script to list all issues and PRs on all my books so they don't fall through the cracks.
Hey all--if you find things wrong, post 'em. I'll clean 'em up. :) Love, Beej
Ok, so unless I'm missing something, this is a big error. In 9.4 there's no way reallinux/master points to same commit as master after the merge. It will still be where it was, one commit behind.
Earlier quoted context omitted.
>It did take maybe a year or so we have normalized this for git - a tool to store versions of text. That’s the problem
Maybe you’re young, but git is better than all of the other shit before it. Try to come up with something simpler than git, and you’ll end up with something like SVN or CVS that struggled with more than a couple of people working on the same files. Try to make something that is more content aware, and you’ll find out how git got its name in the first place.
Are you concerned that your git exposition is much longer than the other guides you have produced?
Earlier quoted context omitted.
Why are programmers so vehemently angry over the fact that a complex tool which does complex things to a complex data structure might have some complexity to it?
"I don't understand this complexity so this means it shouldn't exist"
I can't help but feel that Git has completely missed the forest through the trees that you can make a 30+ part guide explaining how to use it.
Honestly, 99% of the pain of git is simply because people use it through the CLI. If you use tortoisegit or a visual tool, you don't need to worry about any of this because its self explanatory, and it becomes trivial to use Learning git like this is honestly just hampering yourself
This is just asking for trouble.
Hey all--if you find things wrong, post 'em. I'll clean 'em up. :) Love, Beej
Not wrong, but since you’re mentioning vim in the context of git, might be worth adding :cq as a way to exit with a non-zero status to prevent git from finishing the commit / operation.
((cd /tmp/t; find . -type f -print) | sort | while read f; do cmp -s {/tmp/t,/tmp/t1}/$f || vim -f -d {/tmp/t,/tmp/x1}/$f 0Earlier quoted context omitted.
There's an issue for the IPC guide on GitHub that's almost a year old with zero reaction.
That's my lowest traction guide, I think, not counting Beej's Guide to Killing Dragons. :) I've fixed it, and wrote a quick script to list all issues and PRs on all my books so they don't fall through the cracks.