conv.

← The whole story
Tech
Git maintainers weigh jumping straight to Git 3.0 after 2.56

LWN details Git 2.56's contents and the Git 3.0 question

1 Sep 18 · 5d ago · 1 article · 1 source · development 1 of 3

Jonathan Corbet's LWN article describes the roughly 700 non-merge commits in the Git 2.56 release candidate — including an experimental 'git history drop' command, new 'git refs' subcommands, and a '--delete-merged' branch option — and explains that Git 3.0 would bring compatibility breaks, most notably switching the default hash function from SHA-1 to SHA-256.

“It is not the most earth-shaking of releases, but the one that follows, which might be the long-awaited Git 3.0, may well be.”

Jonathan Corbet

Junio Hamano Git project maintainerJonathan Corbet LWN editor and author of the article

The whole story articlesposts the bright band is this development · numbered dots are the others · click one to jump

Peak 5 pieces in two hours at Sep 22, 1 AM; 37 pieces over 6 days (2 articles · 5 posts · 30 comments) Sep 18, 9 AM — 1 piece · 1 article — Newswires 1Sep 18, 11 AM — quietSep 18, 1 PM — quietSep 18, 3 PM — quietSep 18, 5 PM — quietSep 18, 7 PM — quietSep 18, 9 PM — quietSep 18, 11 PM — quietSep 19, 1 AM — quietSep 19, 3 AM — quietSep 19, 5 AM — quietSep 19, 7 AM — quietSep 19, 9 AM — quietSep 19, 11 AM — quietSep 19, 1 PM — quietSep 19, 3 PM — quietSep 19, 5 PM — quietSep 19, 7 PM — quietSep 19, 9 PM — quietSep 19, 11 PM — quietSep 20, 1 AM — quietSep 20, 3 AM — quietSep 20, 5 AM — quietSep 20, 7 AM — quietSep 20, 9 AM — quietSep 20, 11 AM — quietSep 20, 1 PM — quietSep 20, 3 PM — quietSep 20, 5 PM — quietSep 20, 7 PM — quietSep 20, 9 PM — quietSep 20, 11 PM — quietSep 21, 1 AM — quietSep 21, 3 AM — quietSep 21, 5 AM — quietSep 21, 7 AM — quietSep 21, 9 AM — quietSep 21, 11 AM — quietSep 21, 1 PM — quietSep 21, 3 PM — quietSep 21, 5 PM — 2 pieces · 1 article · 1 post — Hacker News 1, Newswires 1Sep 21, 7 PM — 3 pieces · 1 post · 2 comments — Hacker News 2, Mastodon 1Sep 21, 9 PM — quietSep 21, 11 PM — 2 pieces · 1 post · 1 comment — Hacker News 1, Lobsters 1Sep 22, 1 AM — 5 pieces · 2 posts · 3 comments — Mastodon 2, Lobsters 2, Hacker News 1Sep 22, 3 AM — 5 pieces · 5 comments — Hacker News 5Sep 22, 5 AM — 4 pieces · 4 comments — Hacker News 3, Lobsters 1Sep 22, 7 AM — 4 pieces · 4 comments — Lobsters 3, Hacker News 1Sep 22, 9 AM — 1 piece · 1 comment — Hacker News 1Sep 22, 11 AM — quietSep 22, 1 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 3 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 5 PM — 1 piece · 1 comment — Lobsters 1Sep 22, 7 PM — quietSep 22, 9 PM — quietSep 22, 11 PM — quietYesterday, 1 AM — quietYesterday, 3 AM — quietYesterday, 5 AM — 3 pieces · 3 comments — Lobsters 3Yesterday, 7 AM — 3 pieces · 3 comments — Lobsters 3Yesterday, 9 AM — quietYesterday, 11 AM — quietYesterday, 1 PM — quietYesterday, 3 PM — quietYesterday, 5 PM — 1 piece · 1 comment — Lobsters 1Yesterday, 7 PM — quietYesterday, 9 PM — quietYesterday, 11 PM — quietToday, 1 AM — quietToday, 3 AM — quiet ◂ 1 earlier23
2Story reaches Hacker News front page3Article also picked up on Lobsters
Sep 19Sep 20Sep 21Sep 22yesterdaynow · 4:47 AM ET

All 3 developments of Git maintainers weigh jumping straight to Git 3.0 after 2.56 →

NewswiresHacker NewsMastodonLobsters