Loss of contextual history about core-plans

[reset]

@miketheman this was mentioned by one of the Habitat team members in our private chat. I made a conscious choice of not preserving the history because 99.9% of it is pre-launch which is very muddy. We had numerous sweeping renames/moves in the codebase and commits which would reference things in this repository that just don't exist. I figured that it would make more sense to ask people to review the history of the original repository if they wanted to go diving into the past 😄.

The PRs in this repo are currently sitting because the discussion was started on Thursday or Friday without follow up just yet because of Canada day and the 4th of July. I didn't want to merge anything ontop of the initial commit in case somebody had strong feelings that are different then mine. Since I don't care/don't find the history useful I'd rather yield to another developer's preference.

If we're worried about me getting git-blamed or getting some fake "git credit", we can change the initial commit to a bot account.

Since you're the second person to mention this we could also just move the history here if people think it'd be better off!

[fnichol]

@miketheman, @reset Done and done. Personally speaking, I need this history when reconstructing why a plan such as gcc or glibc is the way it is and who was involved in the chain of patches working backwards.

[miketheman]

@reset @fnichol Thanks! I understand the motivations, and appreciate it!

[reset]

No problem at all man!