Katee/git-bomb
View on GitHub ↗ ★ 418
A (nearly) uncloneable repo
5 mentions on Hacker News by 5 people: 0 stories, 5 comments · first 2017-10-12 · latest 2017-10-13
20082026
-
…# 100 MB % ulimit -l $((100 * 1024)) # 100 MB % ulimit -v $((100 * 1024)) # 100 MB % git clone https://github.com/Katee/git-bomb.git Cloning into 'git-bomb'... remote: Counting objects: 18, done. remote: Compressing objects: 100% (6/6),…
comment by pmoriarty · 2017-10-13 · in Exploding Git Repositories -
…latest commit..." message. Curiously, go one level deeper and the commit message is again correct. https://github.com/Katee/git-bomb/tree/master/d0/d0 (INB4 The article suggests Github is aware of this repo, so I have no qualms posting…
comment by TeMPOraL · 2017-10-13 · in Exploding Git Repositories -
Bare for the win. git clone https://github.com/Katee/git-bomb.git --bare
comment by emeraldd · 2017-10-13 · in Exploding Git Repositories -
Good point. For those that are curious: Clone (--no-checkout): $ git clone --no-checkout https://github.com/Katee/git-bomb.git Cloning into 'git-bomb'... remote: Counting objects: 18, done. remote: Compressing objects: 100% (6/6), done.…
comment by yes_or_gnome · 2017-10-12 · in Exploding Git Repositories -
I too was curious about this. https://github.com/Katee/git-bomb/commit/45546f17e5801791d4b... shows: "Sorry, this diff is taking too long to generate. It may be too large to display on GitHub." ...so they must have some kind of backend…
comment by enzanki_ars · 2017-10-12 · in Exploding Git Repositories