Merge remote-tracking branch 'nouiz/doc_update'

doc/index.txt

@@ -100,11 +100,13 @@ Community
     (theano-users, Aug 2, 2010)
 
 
+* Register to `theano-announce`_ if you want to be kept informed on important change on theano(low volume).
+
 * Register and post to `theano-users`_ if you want to talk to all Theano users.
 
 * Register and post to `theano-dev`_ if you want to talk to the developers.
 
-* Register to `theano-announce`_ if you want to be kept informed on important change on theano(low volume).
+* Register to `theano-github`_ if you want to receive an email for all change to the github repository.
 
 * Register to `theano-buildbot`_ if you want to receive our daily buildbot email.
 
@@ -136,6 +138,7 @@ Community
 .. _theano-dev: http://groups.google.com/group/theano-dev
 .. _theano-users: http://groups.google.com/group/theano-users
 .. _theano-announce: http://groups.google.com/group/theano-announce
+.. _theano-github: http://groups.google.com/group/theano-github
 .. _theano-buildbot: http://groups.google.com/group/theano-buildbot
 .. _tickets: http://pylearn.org/theano/trac/query?status=accepted&status=assigned&status=new&status=reopened&group=milestone&max=200&col=id&col=summary&col=status&col=owner&col=type&col=priority&col=component&col=time&report=9&order=priority
 

doc/internal/dev_start_guide.txt

@@ -37,6 +37,12 @@ except that we don't use the numpy docstring standard.
 We do not plan to change all existing code to follow this coding
 style, but as we modify the code, we update it accordingly.
 
+Mailing list
+------------
+
+See the theano main page for the theano-dev, theano-buildbot and
+theano-github mailing list. They are usefull to Theano contributor's.
+
 Typical development workflow
 ----------------------------
 
@@ -145,7 +151,7 @@ circumvent circular dependencies might make it so you have to import files in
 a certain order, which is best handled by the package's own ``__init__.py``.
 
 More instructions
-=================
+-----------------
 
 Once you have completed these steps, you should run the tests like this:
 
@@ -181,7 +187,7 @@ Keep in mind that this branch should be "read-only": if you want to patch
 Theano, do it in another branch like described above.
 
 Nightly test
-============
+------------
 
 Each night we execute all the unit tests automatically.  The result is sent by
 email to the `theano-buildbot`_ mailing list.
@@ -190,3 +196,12 @@ email to the `theano-buildbot`_ mailing list.
 
 For more detail, see :ref:`see <metadocumentation_nightly_build>`.
 
+To run all the test with the same configuration as the buildbot, run this script:
+
+.. code-block:: bash
+
+   theano/misc/do_nightly_build
+
+This function accept argument that it forward to nosetests. So you can
+run only some tests or enable pdb by giving the equivalent nosetests
+parameters.

doc/library/sparse/index.txt

@@ -55,17 +55,14 @@ Some documentation for sparse has been written
 
 
 ===================================================================
-:mod:`sparse.sandbox` --  Sparse Op
+:mod:`sparse` --  Sparse Op
 ===================================================================
 
-.. module:: sparse.sandbox
+.. module:: sparse
    :platform: Unix, Windows
    :synopsis: Sparse Op
 .. moduleauthor:: LISA
 
-API
-===
-
 .. automodule:: theano.sparse.basic
     :members:
 

doc/library/tensor/basic.txt

@@ -924,15 +924,15 @@ The bitwise operators possess this interface:
 
 .. function:: bitwise_and(a, b)
 
-   Alias for and_. bitwise_and is the numpy name.
+   Alias for `and_`. bitwise_and is the numpy name.
 
 .. function:: bitwise_or(a, b)
 
-   Alias for or_. bitwise_or is the numpy name.
+   Alias for `or_`. bitwise_or is the numpy name.
 
 .. function:: bitwise_xor(a, b)
 
-   Alias for xor_. bitwise_xor is the numpy name.
+   Alias for `xor_`. bitwise_xor is the numpy name.
 
 .. function:: bitwise_not(a, b)