5 ms·

they do all the time for other open source projects, I assume this is just legacy that plugs in with their in-house system.

• duskwuff 6y ago
  They could very well be using Git internally. But they don't want to release the full history of their development process, complete with authors, commit messages, and intermediate commits -- that's likely to include or imply a lot of information that isn't appropriate to release.
  • zinekeller 6y ago
    See also: Google and the non-kernel part of AOSP (it is just a snapshot of the current source at the time, not the in-between releases).
    • kdrag0n 6y ago
      Most internal commit history is intact in AOSP, including the changes between releases. They just have a complex merging setup that deviates slightly from internal branches.
  • mikepurvis 6y ago
    Indeed, and this is so much an industry standard practice that it was particularly significant when Apple open sourced Swift in Dec 2015, they didn't just do a tarball dump or promise that development would be in the open going forward, they actually opened up the whole development history right back to the start of the project in 2010: https://github.com/apple/swift/commit/afc81c1855bf711315b8e5de02db138d3d487eeb https://github.com/apple/swift/commit/afc81c1855bf711315b8e5...
    • favorited 6y ago
      Not really unprecedented though. I'm pretty sure the whole SVN repositories were published for clang, libc++, etc. when they were open sourced.
      • deleted 6y ago
        [deleted]
  • fooker 6y ago
    They do, Apple has an internal gitlab instance which a bunch of teams use.