[LLVMdev] LLVM documentation work help

[Sean Silva]

It looks like things are going well.

One suggestion. Instead of using `.. literalinclude::` for displaying
the terminal sessions, you can use `.. code-block:: bash` instead. The
reason that uvbook uses `.. literalinclude` is that they are showing
parts of real compilable programs. If you just want to show a snippet
of code or terminal snippet, you can use `.. code-block::` and avoid
having lots of little files.

-- Sean Silva

On Thu, Nov 29, 2012 at 10:43 AM, Jonathan <gamma_chen at yahoo.com.tw> wrote:
> Sean,
>
> By try, I seems realize the github.com is free for register. So, just ignore my last mail.
>
> Anoushe,
>
> You can register with email and get an account on
> https://github.com/
>
> I have put the our document reStructuredText on git.hub.com. You can clone it without register.
> After you get an account and I add it to collaborators, then you can do check in with our project as follows,
>
> https://github.com/Jonathan2251/lbd.git
>
> Jonathan
>
> On 2012/11/29, at 下午7:13, Sean Silva <silvas at purdue.edu> wrote:
>
>>> I am happy to introduce Anoushe, my llvm backend documentation work helper for English and edit.
>>
>> Awesome! Great to see people helping out. Thank you both for working on this.
>>
>>> Is it possible, me and Anoushe can get a git free space and access right for the reStructuredText files (include .png pictures) of me and Anoushe create in future? If not allowed. Can we hand over the reStructuredText files, and put to git server through you?
>>
>> I would suggest that you create a git repository on github. LLVM
>> itself does not have any git servers except for hosting the SVN
>> mirror.
>>
>> If you want, I can setup a git repository and give you access if you
>> think it would be easier that way. Just tell me what seems easiest for
>> you.
>>
>> -- Sean Silva
>