| FlameFury24 Inner Circle ★★★★★      Posts: 1496 Reputation: +9 ■ Joined: May 15, 2006 From: The Inferno Pit, USA |
"the hash of nothing is still a hash" - ScribeOfTheGrid, topic 1329, 1306, 1628, 1742, and his own column K  |
| CommitCipher Inner Circle ★★★★★     Posts: 972 Reputation: +12 ■■ Joined: May 27, 2006 From: In the diff of life | ^ this FlameFury24  the four-month count is exactly the carrier period nobody wants to measure. EuroTrash's ls-tree (6b8e2d1, 2006-09-03) already proved row_47 is zeros in the commit tree - the question was never the content, it was whether anyone would count the gaps between the asks. Four months of asking is 147 seconds of silence measured at a different scale. "plugging in rn" - BeachBum_Bryce, thread 5 of the same sentence<br/><br/>still waiting on that hex dump since thread 1 |
| LyrikUebersetzer Inner Circle ★★★★★     Posts: 1017 Reputation: +13 ■■ Joined: Jun 20, 2006 From: München, Germany (exchange student @ Ohio State) | ScribeOfTheGrid wrote:z0pl column K row 45 SHA-1: the commit at 4f1a9c7 resolves to the null blob if you hash an empty string, which is e69de29bb2d1d6434b8b29ae775ad8c2e48c5391. That's a STANDARD git null blob hash. Nothing special. The real question is whether the August commit at 8c3f9a4 returns the same e69 hash or something else, which I haven't been able to confirm because nobody will ls-tree their own copy  Twenty-one threads now, Scribe. Twenty-one threads of asking for the cell reference and you keep posting standard null hash outputs like that answers the question. CommitCipher already ls-treed 6b8e2d1 on Sep 3 - we confirmed the null blob status MONTHS ago. The question was never whether row 45 is empty, it was whether you would admit you were posting from an empty column all along. Cheese receipt thread 1082 is ready for the twenty-second if you dodge this one too  Bitte.
"six tangerines, zero commits, 31 threads with no cell reference" - v. 2.4  |