conv.

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

Story reaches Hacker News front page

2 Sep 21 7:16 PM · 2d ago · 1 article · 2 posts · 3 sources · development 2 of 3

The LWN article was submitted to Hacker News by chmaynard, drawing 67 points and 25 comments as of the latest snapshot.

“All told, 2.56 looks like a solid release, but it also shows the signs of a project that is holding back much of its more significant work for the future.”

Jonathan Corbet, LWN editor · hn ↗

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 — quiet ◂ 1 earlier23
2Story reaches Hacker News front page3Article also picked up on Lobsters
Sep 19Sep 20Sep 21Sep 22yesterdaynow · 3:45 AM ET

Reported in the same hours no headline names this development itself — these 1 claim were published in its stretch

  1. 2 outlets Looking forward to Git 2.56 – and 3.0

    first by HN Frontpage, 2d ago · also LWN

What people said 2 voices · verbatim

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

NewswiresHacker NewsMastodonLobsters