Looking forward to Git 2.56 – and 3.0

cchmaynard about 2 hours ago 6 commentsRead Article on lwn.net

DE version is available. Content is displayed in original English for accuracy.

⚡ Community Insights

Discussion Sentiment

50% Positive

Analyzed from 53 words in the discussion.

Discussion (6 Comments)Read Original on HackerNews

KolmogorovComp•about 1 hour ago

Does it mean that when switching trop sha1 to sha256 you need to forcepush and rewrite all history? Wouldn’t that be a massive source of potential vulnerabilities?

nomel•about 1 hour ago

I don't know much about this. How does that enable vulnerabilities exactly?

jayd16•about 1 hour ago

Trusting a forced push w/o any other verification means nefarious history changes can be slipped in.

WCSTombs•about 1 hour ago

`git add --resolved` is a wonderful idea, and definitely something I would start using.