Update llvm-libc status with code repo and mailing list information.

[MaskRay]

llvm/docs/Proposals/LLVMLibC.rst

122

http://lists.llvm.org/pipermail/llvm-dev/2019-July/133840.html

SVN will be retired on Oct 21, 2019

We probably should not add new references to the SVN repository.

[sivachandra]

Do not talk about the SVN repo.

[sivachandra]

Will put this in on Monday if there no objections.

llvm/docs/Proposals/LLVMLibC.rst

 
 There are a few problems one needs to be mindful of when implementing such a
 delegation scheme in llvm-libc. Examples of such problems are:
 
 1. One cannot mix data structures from llvm-libc with those from the
 system-libc. A translation from one set of data structures to the other should
 happen internal to llvm-libc.
 2. The delegation mechanism has to be implemented over a related set of
-functions. For example, one cannot delegate just the `fopen` function to the
-system-libc. One will have to delegate all `FILE` related functions to the
+functions. For example, one cannot delegate just the ``fopen`` function to the
+system-libc. One will have to delegate all ``FILE`` related functions to the
 system-libc.
 
 Current Status
 ==============
 
-llvm-libc development is still in the planning phase.
+llvm-libc development is still in very early stages. The source code can be
+found in the top level directory named ``libc`` in the LLVM monorepo. There
+are also dedicated mailing lists one for dev discussions:
+https://lists.llvm.org/cgi-bin/mailman/listinfo/libc-dev, and another for
+commits: https://lists.llvm.org/cgi-bin/mailman/listinfo/libc-commits.
 
 Build Bots
 ==========
 
 Once the development starts, there will be llvm-libc focused builders added to
 the LLVM BuildBot.