Changes between Version 1 and Version 2 of 2009-10-23-batman-goes-mainline

Show
Ignore:
Timestamp:
03/29/10 16:40:19 (6 months ago)
Author:
marek (IP: 61.59.128.157)
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • 2009-10-23-batman-goes-mainline

    v1 v2  
    22= B.A.T.M.A.N. goes mainline = 
    33 
    4 Since its existance the batman-adv kernel module has been residing outside of[[BR]] 
    5 the linux kernel and needed to be downloaded / compiled / installed seperately.[[BR]] 
    6 We intend to change this by merging the batman-adv kernel module into the[[BR]] 
    7 linux mainline tree. Greg Kroah Hartman has [https://lists.open-mesh.net/pipermail/b.a.t.m.a.n/2009-August/001706.html agreed] to include the module as[[BR]] 
    8 part of the staging drivers as a first step.[[BR]] 
     4{{{ 
     5#!div style="width: 40em; text-align: justify" 
     6 
     7Since its existance the batman-adv kernel module has been residing outside of the linux kernel and needed to be downloaded / compiled / installed seperately. We intend to change this by merging the batman-adv kernel module into the linux mainline tree. Greg Kroah Hartman has [https://lists.open-mesh.net/pipermail/b.a.t.m.a.n/2009-August/001706.html agreed] to include the module as part of the staging drivers as a first step. 
    98 
    109 
     
    1211 
    1312 * Bringing the 0.2 release into staging asap. 
    14  * After gathering feedback from other kernel hackers build patches on top[[BR]] 
    15  of 0.2 to conform with the linux kernel coding style & rules. The result will[[BR]] 
    16  be version 0.2.5. 
    17  * In parallel we will start the 0.3 branch in which new features can be[[BR]] 
    18  included as well as the linux patches from the 0.2.5 branch. 
     13 * After gathering feedback from other kernel hackers build patches on top of 0.2 to conform with the linux kernel coding style & rules. The result will be version 0.2.5. 
     14 * In parallel we will start the 0.3 branch in which new features can be included as well as the linux patches from the 0.2.5 branch. 
    1915 
    2016 
    2117'''How are we going to tackle this ?''' 
    2218 
    23 As the kernel developers prefer git over SVN we created our own git repository[[BR]] 
    24 which imports all changes from our SVN to make backporting changes as easy[[BR]] 
    25 as possible. git allows us to manage different patchesets for the kernel hackers.[[BR]] 
    26 Checkout http://git.open-mesh.net to get the git repository and [wiki:UsingBatmanGit learn how to use it]. 
     19As the kernel developers prefer git over SVN we created our own git repository which imports all changes from our SVN to make backporting changes as easy as possible. git allows us to manage different patchesets for the kernel hackers. Checkout http://git.open-mesh.net to get the git repository and [wiki:UsingBatmanGit learn how to use it]. 
    2720 
    2821 
     
    3023 
    3124We maintain a TODO file in the git repository that you can see here: 
     25}}} 
    3226 
    3327[[Include(http://git.open-mesh.net/TODO.html)]] 
    3428 
    35 If you are interested in helping us out you can grab one item, make a patch[[BR]] 
    36 and send it to our [wiki:MailingList Mailinglist]. 
     29{{{ 
     30#!div style="width: 40em; text-align: justify" 
     31 
     32If you are interested in helping us out you can grab one item, make a patch and send it to our [wiki:MailingList Mailinglist]. 
     33}}}