Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Highlights from Git 2.28

github.blog

Post reply on HN
Print view View original

121–130 of 147 posts

Re: Highlights from Git 2.28

#121

Post by globular-toast »

WorldMaker wrote: post #74
sildur wrote: post #70

Earlier quoted context omitted.

In the rest of the world is not as problematic, as we associate master with teacher. But we are used to America forcing their culture down our throats. Like they did when tried to force down their hatred for the police on us. So, another one to the list. It would be nice if some day they tried to consider how the rest of the world sees things. For a change.

> 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…

What? Apartheid wasn't slavery. And since when do South Africans want to change the language to bury the past?

Re: Highlights from Git 2.28

#122

Post by jmiserez »

_ZeD_ wrote: post #85
jancsika wrote: post #9

Someone 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…

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.

Re: Highlights from Git 2.28

#125

Post by franga2000 »

romanoderoma wrote: post #53
Twisol wrote: post #38

Earlier quoted context omitted.

I can appreciate that "canon" is used in religious contexts, but its meaning and origin go back further than that. Wiktionary (hardly the best source, I know) lists three secular meanings before the religious ones begin. The most relevant is this one: > A group of literary works that are generally accepted as representing a field. Also, the coinage "fanon" (as in derivative works by a fanbase) comes directly from the…

> 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 can't win this...

Re: Highlights from Git 2.28

#126

Post by mekster »

It's sad to see people complain about git for complication because people just jumped on the "It's made for kernel development by Linus, so it should work for me" bandwagon when he wasn't obviously targeting for the masses...

For sake, I was using bazaar back then as it looked to be aiming to be user friendly but I guess everyone jumping to git killed it.

Now every new git users are crying how it's not intuitive while every developer ecosystem is being built around git.

It's the price we pay for blindly following "coolness".

Re: Highlights from Git 2.28

#127

Post by crististm »

gempir wrote: post #118
war1025 wrote: post #104

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.

This change isn't done because master is super offensive or racist in the context of git. It's done to show some kind of support to the movement. Might not much very much, but I think showing you care is something. If it breaks a bit of shitty tooling that relies on hardcoded values, then I think we can live through that.

I think that propaganda got the better of you. But I can live with that if you can.

Re: Highlights from Git 2.28

#128

Post by nine_k »

jayd16 wrote: post #76
lilyball wrote: post #60

Earlier quoted context omitted.

> Its not easy to set up git config settings for a distributed team. I assume for security reasons a repo can't configure its own settings just from a pull but even still I want that functionality. Git settings can do a lot, including running arbitrary commands. Having this set up automatically is a massive security issue. Put a script in your repo somewhere and instruct people to run the script after cloning. > Why…

>Because the configuration may be different from machine to machine This is the crux of the issue. I want something to ensure turn-key configuration in a secure and cross platform way. Maybe github/gitlab could generate something like an installer script instead of just a clone url.

Do you have a cross-platform package manager?

One such package manager can be npm (if you use Node anyway), it can install and run scripts.

But having to run a setup script once could be massively simpler, though less flexible.

Re: Highlights from Git 2.28

#129

Post by jayd16 »

MarkSweep wrote: post #107
jayd16 wrote: post #98

Earlier quoted context omitted.

What does worktree provide that a fresh local clone doesn't?

If it's a multi-gigabyte repo that you are cloning over a slow VPN, it speeds things up quite a bit.

Like I said, I'd usually just clone locally, as in clone from the repo you already have on disk.

Re: Highlights from Git 2.28

#130

Post by jayd16 »

fiddlerwoaroof wrote: post #103
jayd16 wrote: post #98

Earlier quoted context omitted.

What does worktree provide that a fresh local clone doesn't?

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.
Post reply on HN