Conversation

Notices

1. Ben Zanin (gnomon@mastodon.social)'s status on Wednesday, 26-Jun-2019 17:57:26 EDT Ben Zanin

   dir='x' ; git init "$dir" && cd "$dir" && git commit --allow-empty -m 'Init' && git reset "$(git cat-file -p HEAD|awk -v tentacles=$((2**16)) -v hash="$(git rev-parse HEAD)" -v ts="$(printf '%(%s)T' -1)" '/^tree /{print;while (tentacles-->0)printf("parent %s\n",hash);next};/^(author|committer) /{$(NF-1)=ts};/^Init/{sub(/.*/,"HORROR")};1'|git hash-object -t commit -w --stdin)"

   1. Ben Zanin (gnomon@mastodon.social)'s status on Thursday, 27-Jun-2019 08:41:31 EDT Ben Zanin

      in reply to

      The above monstrosity creates an empty repo with two commits in it, an initial commit and then a merge commit. The merge commit is odd in two significant ways:

      1. every one of its parent commits are the same, they're all the initial empty commit
      2. the merge commit has 65,536 parent commits

      Running 'git log --graph' in the repo is _hilarious_

      1. Ben Zanin (gnomon@mastodon.social)'s status on Thursday, 27-Jun-2019 08:42:18 EDT Ben Zanin

         in reply to

         I would say "blame @JordiGH" but that's not fair, it's not actually his fault

         Mostly not