141–147 of 147 posts
Earlier quoted context omitted.
Reduced disk space usage for large repositories. And a convenient way to manage all your clones
I guess it reduces duplicating the history? Large files are by far the bulk of what I personally deal with so it don't think there's a real difference for me but I could see it helping.
Earlier quoted context omitted.
I feel like on the one hand my opinion is "this is stupid and doesn't matter", which makes me think the change was not needed. But also my opinion is "this is stupid and doesn't matter", which makes me not really care that they did I guess.
I care if stuff breaks for no good reason and this is one of them. But Microsoft is establishing a history of being political correct instead of doing the sensible thing. Calling the default branch master is a design choice and nothing more, if you think otherwise the problem is yours.
What if the default branch was called "slut" or "faggot" for whatever reason?
Earlier quoted context omitted.
> In the rest of the world is not as problematic, as we associate master with teacher. Every word has more than one association. The argument is not that every association for the word is negative, but that one association is extremely negative, and we have the ability to use words that have fewer negative associations, so why shouldn't we use words with fewer negative associations? That extremely negative associatio…
Ah, yes. The old “if you don’t think like me you are wrong.” We are also used to that condescending attitude. Very American. But, as surprising as may be, there are other cultures in this world. In mine, master is a word associated to teacher. You see the issue as more recent because it is happening right now. The scars are still bleeding. Maybe this is why you all overreact so much to simple words. To overcompensate…
Do whatever you like. I'm not telling you what to do. I'm not telling anyone what to do. I was merely explaining the controversy. I give up. I do not understand what all this hate is about. I'm just the messenger, but I guess I can take all the shots.
I wonder about which primary branch naming convention they’ll arrive at. “primary” is my personal favorite ;)
At Elementary we've adopted `latest` as it tracks nicely with the bleeding-edge tag for Docker containers which we don't have control over. This way, when we build/deploy containers off of the `latest` branch there's an equivalent tag on our DockerHub repos. https://github.com/elementary-robotics/atom
Earlier quoted context omitted.
>> First, the simple optimization for Linux systems: double-click on the commit hash, q, git show, middle-click to paste. That's a simpler copy-paste. I do that surprisingly often, when browsing repositories. Yes, I also double-click on the commit hash and copy it. But I wish there was an incrementing index starting from the top of git log, such that say the 15th commit down, I could just say `git show 15` and see th…
If you want to navigate without using the mouse, I'd definitely suggest using vim-fugitive, or tig, or any number of git interfaces that let you browse with keyboard shortcuts.
I guess if there was one git wrapper that I could use for everything, that would be better. But then I would be probably forget all the traditional git commands, and would be useless if I had to jump on another machine.
Earlier quoted context omitted.
git diff --color-moved This makes git diff highlight reindented or moved lines differently. I use it to get diffs similar to when you pass -w, but with a bit more context. It takes a bit of experimenting to keep it from looking like a fruit salad, but sometimes you get interesting results. https://git-scm.com/docs/git-diff#Documentation/git-diff.txt...
If you use git diffs frequently, I recommend setting up delta: https://github.com/dandavison/delta
I'm a somewhat advanced user of Git. My coworkers use me as a reference when they have a problem of a difficult merge to solve. I don't follow each Git release, but I also didn't notice a great productivity enhancement for a long time. Sure it is a sign of a mature project, but I'd like to know: What's the somewhat recent Git feature that you really improved your productivity?
git restore
It's not just better name for doing "git checkout -- path". "git checkout" has this stupid behavior of restoring files to worktree and index. "git restore" by default doesn't touch index (I wrote SO answer that explains this a bit more: https://stackoverflow.com/a/60855504/350384)
there is also "git switch" but I just kept using "git checkout" because there is nothing "git switch" can do that "git checkout" can (it's just a shorter name but I had aliased "checkout" to "ch" anyway, as many people do)