Wish they'd bake in some sort of a solution for managing huge files. A lot of people have this problem.
LFS?
Not baked in. Also, unreliable and slow.
Highlights from Git 2.28
131–140 of 147 posts
Re: Highlights from Git 2.28
#132Earlier quoted context omitted.
IMHO the only problem is what people wanna see in words. master/slave has been with us since forever ( https://news.ycombinator.com/item?id=23969906 ) and describes a relationship between two entities where one is the controller and the other is controlled, in many religions (including the most popular one) there is still a master God (or more than one) and believers are slave to God (with the capital G) But in Git t…
Bitkeeper, which early git developers were familiar with, did use master in a master/slave relationship. While git does not enforce such "hierarchy", there remains an association (both in how we use the word outside of the context of git as well as historically in how the word was used by predecessor SCSes). > master/slave has been with us since forever "Tradition" or "we've always done it that way" is not a great ex…
> bitkeeper
This was refuted by the person who named it- https://mobile.twitter.com/xpasky/status/1272280760280637441
This argument comes off as very condescending in a soft bigotry of low expectations-type of way, given there's nothing else within git that even hints to master being related to master-slave terminology.
Re: Highlights from Git 2.28
#133Earlier quoted context omitted.
git switch/git switch -c so much better than git checkout and the confusing switches.
Not for me. Those confusing switches are already ingrained in my memory (or hidden away behind aliases) and now I find it more confusing that git is recommending new and different commands to do things that I've been doing a fixed way for years. `git restore ` instead of `git checkout -- `is another one.
well git checkout basically is confusing because it does two things at once.
git restore and git switch basically tries to seperate the functionality.
i.e. from: "git-checkout - Switch branches or restore working tree files"
to
- "git-switch - Switch branches"
- "git-restore - Restore working tree files"
tbf I found it really stupid from the beginning that it tries two things at once.
Re: Highlights from Git 2.28
#134Earlier quoted context omitted.
IMHO the only problem is what people wanna see in words. master/slave has been with us since forever ( https://news.ycombinator.com/item?id=23969906 ) and describes a relationship between two entities where one is the controller and the other is controlled, in many religions (including the most popular one) there is still a master God (or more than one) and believers are slave to God (with the capital G) But in Git t…
Bitkeeper, which early git developers were familiar with, did use master in a master/slave relationship. While git does not enforce such "hierarchy", there remains an association (both in how we use the word outside of the context of git as well as historically in how the word was used by predecessor SCSes). > master/slave has been with us since forever "Tradition" or "we've always done it that way" is not a great ex…
> especially when part of the problem is systemic papercuts
I'm sorry for slavery in US, but slavery in US is hardly the only example of slavery in history.
master/slave describes more than just a hundred years of slavery in United States
It also describes thousands of years of religious beliefs, for example.
> the very point of questioning it is whether or not this "tradition" is worth the pain of systemic papercuts
Not to sound harsh, but 5 billion people are ok with it.
It's a linguistic problem for a small minority of the population that speaks English as a native language and super charge words meaning.
Take for example the word servomotor.
A servomotor is
> French servo-moteur, from Latin servus slave, servant + French -o- + moteur motor, from Latin motor one that moves
In Italian it is "servo motore", servo is the exact translation of slave.
Why is servomotor ok, why is "I'm a slave to Jesus" or "God is my master" ok, but master branch is not?
I'm simply curious of why some people can't let things go...
Re: Highlights from Git 2.28
#135Earlier quoted context omitted.
> but its meaning and origin go back further than that master/slave goes back to Mesopotamia, 4 thousands years ago and was used to describe the relationship between men and gods > Man was believed to have been created to serve the gods, or perhaps wait on them: the god is lord or master (belu) and man is servant or slave (ardu) I guess being that old is not good enough nowadays
But git doesn't use master/slave (noun). It uses master as an adjective ("master branch"). Think cassettes and vinyl records or "master boot record". It means being the definitive source of truth and has been used in that form for centuries [citation needed, but I don't remember where I read it]. This isn't just an instance of "not old enough", it's an instance of it not even being the same word, so I guess you just…
Yep
I made the same point here
Re: Highlights from Git 2.28
#136Earlier quoted context omitted.
Bitkeeper, which early git developers were familiar with, did use master in a master/slave relationship. While git does not enforce such "hierarchy", there remains an association (both in how we use the word outside of the context of git as well as historically in how the word was used by predecessor SCSes). > master/slave has been with us since forever "Tradition" or "we've always done it that way" is not a great ex…
> especially when part of the problem is systemic papercuts I'm sorry for slavery in US, but slavery in US is hardly the only example of slavery in history. master/slave describes more than just a hundred years of slavery in United States It also describes thousands of years of religious beliefs, for example. > the very point of questioning it is whether or not this "tradition" is worth the pain of systemic papercuts…
Paul Graham published an essay recently which describes these kind of people as "aggressively conventionally-minded": http://paulgraham.com/conformism.html
Essentially there are some people who will follow rules and trends without questioning them. Among those there are some who will actively seek to punish those who do not follow the rules.
This master/slave thing is a new rule born out of guilt and virtue signalling. This comes from the fact that some people see themselves as genuinely superior to others and this makes them uncomfortable. They virtue signal in an attempt to fight against this feeling, rather than just accepting what may be true, moving on, and continuing to be a good person. It's a phenomenon that has been observed in many contexts. The most vocal homophobes are often homosexual themselves. The most vocal religious devotees often have the strongest doubts.
Re: Highlights from Git 2.28
#137Earlier quoted context omitted.
Have you tried graphical git clients? Try the Eclipse git plugin. For real! It's the most intuitive tool to deal with git histories
Yes, but IntelliJ's "Show History for Selection" takes the cake. It opens up a timemachine-like view that shows just the changes/commits affecting that block and lets you scroll through them.
nope.
I have used intellij. Its git plugin support its... mediocre at best.
Try eclipse.
Re: Highlights from Git 2.28
#138Earlier quoted context omitted.
Yes, but IntelliJ's "Show History for Selection" takes the cake. It opens up a timemachine-like view that shows just the changes/commits affecting that block and lets you scroll through them.
nope. I have used intellij. Its git plugin support its... mediocre at best. Try eclipse.
I use both daily. Eclipse doesn't have that specific feature.
Re: Highlights from Git 2.28
#139Someone please give me the missing link here: 1. I do `git log` which helpfully pipes to `more` where I can use vim-stsyle search to find the commit I'm interested in. 2. I find the relevant commit. 3. Now I want to `git show` that commit. Currently I double click on the human unreadable commit, copy it, quit `more` to get back to the command line, type `git show`, then paste the commit. Navigate, click-click, shortc…
By using a smarter tool. I personally use magit, which solves this problem across all of git, but it's tied to Emacs. tig is a git log browser I've heard good things about that seems to handle this use case very nicely. You may also be able to pervert less into making this easier, e.g. by using lesskey(1) to add a keybinding that runs `git show $(xclip -o)`. I don't know how wise that would be.
Yeah, tig is awesome and I use it exactly for this use case.
For what I see, magit is way ahead when it comes to the feature set, but tig has the killer feature of having a completely flat learning curve (and I say this as an Emacs user): 1) type tig 2) use arrows to move between commits and page up/down to move within diffs. That's all!
Re: Highlights from Git 2.28
#140I'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?
Sparkle/partial checkout for big repo or legacy or people doing shit with git