summaryrefslogtreecommitdiffstats
path: root/llvm/docs/Proposals
Commit message (Collapse)AuthorAgeFilesLines
* fix various typosSylvestre Ledru2017-06-261-1/+1
| | | | llvm-svn: 306262
* [Docs] Add VectorizationPlan to docs/Proposals.Ayal Zaks2017-05-291-0/+182
| | | | | | | | Following the request made in https://reviews.llvm.org/D32871, the general documentation of the Vectorization Plan is hereby placed under docs/Proposals. llvm-svn: 304161
* fix some typos in the docSylvestre Ledru2017-01-141-2/+2
| | | | llvm-svn: 292014
* [doc] use double `` to prevent html output of merging double dashMehdi Amini2016-10-171-3/+3
| | | | llvm-svn: 284412
* [GitHubMove Doc] Properly nest a subsection in the proposalMehdi Amini2016-10-121-1/+1
| | | | llvm-svn: 284082
* Moving to GitHub - Unified ProposalMehdi Amini2016-10-122-273/+868
| | | | | | | | | | | | | | | This document describes the proposal to move to GitHub, and compare the two proposals through various workflow examples, presenting the current set of commands following by the ones involved in each of the two proposals. It is intended to supersede the previous "submodule proposal" document entirely, and drive the discussion at the BoF during the next Dev Meeting. Differential Revision: https://reviews.llvm.org/D24167 llvm-svn: 284077
* [docs] Add sub-mod example by Chris to GitHub proposalRenato Golin2016-07-281-0/+5
| | | | llvm-svn: 277032
* fix some typos in the docSylvestre Ledru2016-07-281-1/+1
| | | | llvm-svn: 276968
* [docs] Move GitHub to GitHubSubModRenato Golin2016-07-211-3/+3
| | | | | | | | Given that other proposals are making their way through, it's better if we specify what GitHub proposal this is, in case there are others that also involve GitHub, but not sub-modules. llvm-svn: 276325
* [docs] GitHub Proposal for LLVMRenato Golin2016-07-201-0/+268
This document was crafted from the various (320+) emails between 2nd June and 20th July regarding the move to GitHub. It tried to consolidate every issue that was raised and every solution that was presented to have a GitHub repository with sub-modules. It *does not* try to argue whether sub-modules are better or worse than any other Git solution, nor if Git is better than any other VCS, nor if GitHub is better than any other free code hosting service. This is just the final conclusions of 48 days and 320 emails (plus a lot of IRC discussions) on the LLVM community. This document will be presented at the survey that the foundation will setup for us to decide if we move to this solution or not. It reflects what was discussed on the lists, but it's not authoritative. If something is not clear enough, please refer to the mailing list discussions (hint: search for "GitHub"). Review: https://reviews.llvm.org/D22463 llvm-svn: 276097
OpenPOWER on IntegriCloud