search for: d44910

Displaying 7 results from an estimated 7 matches for "d44910".

2018 Mar 29
4
[RFC] Markdown for documentation
There's been some desire recently to start writing documentation in Markdown instead of reStructuredText. I put up a [patch]( https://reviews.llvm.org/D44910) for that, but we should figure out a policy on how we want our documentation written first. The desire to use Markdown comes mostly from it being simpler, and having much wider adoption. It does lack some of the feature that reStructuredText has; however, the recommonmark plugin for Sphinx adds...
2018 Mar 29
2
[RFC] Markdown for documentation
...el Spencer via llvm-dev > <llvm-dev at lists.llvm.org <mailto:llvm-dev at lists.llvm.org>> wrote: > > There's been some desire recently to start writing documentation > in Markdown instead of reStructuredText. I put up a > [patch](https://reviews.llvm.org/D44910) for that, but we should > figure out a policy on how we want our documentation written first. > > The desire to use Markdown comes mostly from it being simpler, and > having much wider adoption.  It does lack some of the feature that > reStructuredText has; however,...
2018 Apr 02
0
[RFC] Markdown for documentation
...gt; On Thu, Mar 29, 2018 at 1:26 PM Michael Spencer via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> There's been some desire recently to start writing documentation in >> Markdown instead of reStructuredText. I put up a [patch]( >> https://reviews.llvm.org/D44910) for that, but we should figure out a >> policy on how we want our documentation written first. >> >> The desire to use Markdown comes mostly from it being simpler, and having >> much wider adoption. It does lack some of the feature that reStructuredText >> has; howev...
2018 Mar 29
0
[RFC] Markdown for documentation
...o .md easily over time. On Thu, Mar 29, 2018 at 1:26 PM Michael Spencer via llvm-dev < llvm-dev at lists.llvm.org> wrote: > There's been some desire recently to start writing documentation in > Markdown instead of reStructuredText. I put up a [patch]( > https://reviews.llvm.org/D44910) for that, but we should figure out a > policy on how we want our documentation written first. > > The desire to use Markdown comes mostly from it being simpler, and having > much wider adoption. It does lack some of the feature that reStructuredText > has; however, the recommonmark...
2018 Apr 02
0
[RFC] Markdown for documentation
...ting books, etc.) - Jessica > On Mar 29, 2018, at 1:25 PM, Michael Spencer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > There's been some desire recently to start writing documentation in Markdown instead of reStructuredText. I put up a [patch](https://reviews.llvm.org/D44910 <https://reviews.llvm.org/D44910>) for that, but we should figure out a policy on how we want our documentation written first. > > The desire to use Markdown comes mostly from it being simpler, and having much wider adoption. It does lack some of the feature that reStructuredText has;...
2018 Apr 02
0
[RFC] Markdown for documentation
...this makes sense. -- adrian > On Mar 29, 2018, at 1:25 PM, Michael Spencer via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > There's been some desire recently to start writing documentation in Markdown instead of reStructuredText. I put up a [patch](https://reviews.llvm.org/D44910 <https://reviews.llvm.org/D44910>) for that, but we should figure out a policy on how we want our documentation written first. > > The desire to use Markdown comes mostly from it being simpler, and having much wider adoption. It does lack some of the feature that reStructuredText has;...
2018 Apr 02
0
[RFC] Markdown for documentation
...rote: > On 29 Mar 2018, at 21:25, Michael Spencer via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > > > > There's been some desire recently to start writing documentation in > Markdown instead of reStructuredText. I put up a [patch]( > https://reviews.llvm.org/D44910) for that, but we should figure out a > policy on how we want our documentation written first. > > > > The desire to use Markdown comes mostly from it being simpler, and > having much wider adoption. It does lack some of the feature that > reStructuredText has; however, the re...