1. 25 Jan, 2019 1 commit
    • Josh Stone's avatar
      Rebase to the llvm-project monorepo · df0466d0
      Josh Stone authored
      The new git submodule src/llvm-project is a monorepo replacing src/llvm
      and src/tools/{clang,lld,lldb}.  This also serves as a rebase for these
      projects to the new 8.x branch from trunk.
      The src/llvm-emscripten fork is unchanged for now.
  2. 02 Jan, 2019 1 commit
  3. 30 Jul, 2018 1 commit
  4. 16 Feb, 2018 1 commit
    • Guillaume Gomez's avatar
      Remove hoedown from rustdoc · 5bd5bc3f
      Guillaume Gomez authored
      Is it really time? Have our months, no, *years* of suffering come to an end? Are we finally able to cast off the pall of Hoedown? The weight which has dragged us down for so long?
      So, timeline for those who need to catch up:
      * Way back in December 2016, [we decided we wanted to switch out the markdown renderer](https://github.com/rust-lang/rust/issues/38400). However, this was put on hold because the build system at the time made it difficult to pull in dependencies from crates.io.
      * A few months later, in March 2017, [the first PR was done, to switch out the renderers entirely](https://github.com/rust-lang/rust/pull/40338). The PR itself was fraught with CI and build system issues, but eventually landed.
      * However, not all was well in the Rustdoc world. During the PR and shortly after, we noticed [some differences in the way the two parsers handled some things](https://github.com/rust-lang/rust/issues/40912), and some of these differences were major enough to break the docs for some crates.
      * A couple weeks afterward, [Hoedown was put back in](https://github.com/rust-lang/rust/pull/41290), at this point just to catch tests that Pulldown was "spuriously" running. This would at least provide some warning about spurious tests, rather than just breaking spontaneously.
      * However, the problems had created enough noise by this point that just a few days after that, [Hoedown was switched back to the default](https://github.com/rust-lang/rust/pull/41431) while we came up with a solution for properly warning about the differences.
      * That solution came a few weeks later, [as a series of warnings when the HTML emitted by the two parsers was semantically different](https://github.com/rust-lang/rust/pull/41991). But that came at a cost, as now rustdoc needed proc-macro support (the new crate needed some custom derives farther down its dependency tree), and the build system was not equipped to handle it at the time. It was worked on for three months as the issue stumped more and more people.
        * In that time, [bootstrap was completely reworked](https://github.com/rust-lang/rust/pull/43059) to change how it ordered compilation, and [the method by which it built rustdoc would change](https://github.com/rust-lang/rust/pull/43482), as well. This allowed it to only be built after stage1, when proc-macros would be available, allowing the "rendering differences" PR to finally land.
        * The warnings were not perfect, and revealed a few [spurious](https://github.com/rust-lang/rust/pull/44368) [differences](https://github.com/rust-lang/rust/pull/45421) between how we handled the renderers.
        * Once these were handled, [we flipped the switch to turn on the "rendering difference" warnings all the time](https://github.com/rust-lang/rust/pull/45324), in October 2017. This began the "warning cycle" for this change, and landed in stable in 1.23, on 2018-01-04.
        * Once those warnings hit stable, and after a couple weeks of seeing whether we would get any more reports than what we got from sitting on nightly/beta, [we switched the renderers](https://github.com/rust-lang/rust/pull/47398), making Pulldown the default but still offering the option to use Hoedown.
      And that brings us to the present. We haven't received more new issues from this in the meantime, and the "switch by default" is now on beta. Our reasoning is that, at this point, anyone who would have been affected by this has run into it already.
  5. 26 Jul, 2017 1 commit
    • Josh Triplett's avatar
      COPYRIGHT: Provide a better explanation of Rust copyrights · f1de27fe
      Josh Triplett authored
      Avoid implying that any copyrights have been assigned to a separate
      entity (such as "The Rust Project Developers") Rust contributors retain
      their copyrights, and do not assign them to anyone by contributing.
      Remove the inaccurate notice, and provide a clear explanation. Avoid
      stating that all files contain copyright notices and/or license notices,
      and especially avoid suggesting that the license terms only apply to
      files marked as such.
      In the process, this also drops a separate notice that implies only some
      copyrights are retained by contributors (suggesting that others are
  6. 20 Jun, 2017 1 commit
    • Alex Crichton's avatar
      Remove the in-tree `flate` crate · a4024c58
      Alex Crichton authored
      A long time coming this commit removes the `flate` crate in favor of the
      `flate2` crate on crates.io. The functionality in `flate2` originally flowered
      out of `flate` itself and is additionally the namesake for the crate. This will
      leave a gap in the naming (there's not `flate` crate), which will likely cause a
      particle collapse of some form somewhere.
  7. 17 Apr, 2017 1 commit
  8. 12 Apr, 2017 1 commit
  9. 28 Jan, 2016 1 commit
  10. 16 Jan, 2016 1 commit
  11. 01 Jan, 2016 1 commit
  12. 08 Sep, 2015 1 commit
  13. 22 Jan, 2015 1 commit
  14. 11 Jan, 2015 1 commit
  15. 06 Oct, 2014 1 commit
  16. 01 Oct, 2014 1 commit
  17. 09 Jan, 2014 1 commit
  18. 04 May, 2013 1 commit
  19. 02 Apr, 2013 1 commit
  20. 04 Dec, 2012 1 commit
  21. 28 Aug, 2012 1 commit
  22. 03 May, 2012 4 commits
  23. 26 Jan, 2012 1 commit
  24. 18 Jan, 2012 1 commit
  25. 09 Jan, 2012 1 commit
  26. 06 Jan, 2012 1 commit
  27. 17 Dec, 2011 1 commit
  28. 30 Nov, 2011 1 commit
  29. 09 Aug, 2011 1 commit
  30. 03 May, 2011 1 commit
  31. 24 Jun, 2010 1 commit
  32. 16 Jun, 2010 1 commit