summaryrefslogtreecommitdiffstats
path: root/.gitattributes (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Mark .fixed files as Rust syntax for GitHubManish Goregaokar2018-05-281-0/+1
|
* GitHub: Stop treating Cargo.lock as a generated file.kennytm2018-05-161-1/+1
| | | | | | We do want to inspect the changes to Cargo.lock, hiding the diff by default would miss important details like https://github.com/rust-lang/rust/pull/50629#discussion_r187556602
* Do not automatically merge Cargo.lockOliver Schneider2017-12-061-0/+1
|
* fix gitattributes for vendorSteve Klabnik2017-02-131-1/+1
|
* rustbuild: Start building --enable-extendedAlex Crichton2017-01-241-2/+1
| | | | | | | | | | | | | | | | | This commit adds a new flag to the configure script, `--enable-extended`, which is intended for specifying a desire to compile the full suite of Rust tools such as Cargo, the RLS, etc. This is also an indication that the build system should create combined installers such as the pkg/exe/msi artifacts. Currently the `--enable-extended` flag just indicates that combined installers should be built, and Cargo is itself not compiled just yet but rather only downloaded from its location. The intention here is to quickly get to feature parity with the current release process and then we can start improving it afterwards. All new files in this PR inside `src/etc/installer` are copied from the rust-packaging repository.
* rustbuild: Tweak for vendored dependenciesAlex Crichton2016-11-081-0/+1
| | | | | | | | | | | | | | | | A few changes are included here: * The `winapi` and `url` dependencies were dropped. The source code for these projects is pretty weighty, and we're about to vendor them, so let's not commit to that intake just yet. If necessary we can vendor them later but for now it shouldn't be necessary. * The `--frozen` flag is now always passed to Cargo, obviating the need for tidy's `cargo_lock` check. * Tidy was updated to not check the vendor directory Closes #34687
* std: Remove msvc/valgrind headersAlex Crichton2015-07-271-2/+0
| | | | | | | These aren't really used for anything any more, so there doesn't seem to be much reason to leave them around in the `rt` directory. There was some limiting of threads spawned or tests when run under valgrind, but very little is run under valgrind nowadays so there's also no real use keeping these around.
* webfonts: proper fixAdrien T├ętar2014-07-081-0/+1
|
* make sure jemalloc valgrind support is enabledDaniel Micay2014-05-111-1/+1
| | | | This requires pointing it at the valgrind headers we carry in-tree.
* gitattributes: rm obsolete jemalloc entryDaniel Micay2014-05-101-1/+0
|
* dist: Tweak the OSX pkg installerAlex Crichton2014-03-281-0/+1
| | | | | | | | This performs a few touch-ups to the OSX installer: * A rust logo is shown during installation * The installation happens to /usr/local by default (instead of /) * A new welcome screen is shown that's slightly more relevant
* drop the linenoise libraryDaniel Micay2013-10-161-1/+0
| | | | Closes #5038
* stop fighting with rust logo filetype.Felix S. Klock II2013-09-251-0/+1
|
* restore auto-detection of text filesDaniel Micay2013-09-191-1/+1
| | | | We force the usage of LF line endings, but *only* in text files.
* gitattributes: force LF line endings for all filesadridu592013-09-161-4/+1
| | | | | | | | This avoids default CRLF on msysgit for Windows which can cause trouble. Cf. https://help.github.com/articles/dealing-with-line-endings#text-eollf Commit dad2ccc9b3b27d3f438eeea53b771cc85f6dfa32 followup. Closes #7723.
* Force line ending of '.in' files in jemalloc to LFMukilan Thiagarajan2013-08-241-0/+3
| | | This fixes issue #8731 . On Windows, if the git option core.autocrlf is true (github recommends users to turn on this flag - see https://help.github.com/articles/dealing-with-line-endings), the headers generated from the .in files will have syntatic errors, causing compilation to fail.
* add jemalloc to the runtimeDaniel Micay2013-06-011-0/+1
|
* add gitattributes and fix whitespace issuesDaniel Micay2013-05-031-0/+9