Repository : ssh://git@open-mesh.org/doc

On branches: backup-redmine/2017-07-13,master

commit 8eafc789796c85a679207ec315bad9f33d20d0e5 Author: Linus Lüssing linus.luessing@c0d3.blue Date: Wed Mar 10 20:03:42 2010 +0000

doc: open-mesh/Gsoc2010-ideas: nah, Turing is only indirectly involved afaik

8eafc789796c85a679207ec315bad9f33d20d0e5 open-mesh/Gsoc2010-ideas.textile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/open-mesh/Gsoc2010-ideas.textile b/open-mesh/Gsoc2010-ideas.textile index e7ecca01..e27f099b 100644 --- a/open-mesh/Gsoc2010-ideas.textile +++ b/open-mesh/Gsoc2010-ideas.textile @@ -3,7 +3,7 @@ * Routing and networking knowledge in general * Programming language: C = Recommended and/or useful = -These things are not a prerequisite but might be very useful and/or have to be learned turing the GSoC anyway. +These things are not a prerequisite but might be very useful and/or have to be learned during the GSoC anyway. * [[http://www.kernel.org/doc/Documentation/CodingStyle Linux kernel coding style]] * Reading the documentation of the algorithms: [[http://gitorious.org/batman-adv-doc batman-adv-doc]] [[http://tools.ietf.org/html/draft-wunderlich-openmesh-manet-routing-00 batman-rfc-draft]] (used in the 'old' batmand) * Being able to use virtual machines for debugging (i.e. qemu)