ContributingCode.wiki
changeset 768 6d2816127552
parent 728 1b0f7b17e748
child 769 ccf2964c7497
equal deleted inserted replaced
767:6ec822593966 768:6d2816127552
    48 In newer versions of Mercurial you can give those unnamed branches a "local" and removable name using {{{hg bookmark}}}.
    48 In newer versions of Mercurial you can give those unnamed branches a "local" and removable name using {{{hg bookmark}}}.
    49 
    49 
    50 *You can see example of how unnamed branches and bookmarks are used best [http://hg.hedgewars.org/hw-example-clone/graph HERE]*
    50 *You can see example of how unnamed branches and bookmarks are used best [http://hg.hedgewars.org/hw-example-clone/graph HERE]*
    51 
    51 
    52 
    52 
    53 = How to make your changes known and available to us  =
    53 = How to export your changes so that we can use them  =
    54 
    54 
    55 TODO: diffs, exported patches, public repo clone, etc.
    55 TODO: diffs, exported patches, public repo clone, etc.
    56 
    56 
       
    57 == Public Repository ==
       
    58 If you setup a public repository e.g. at github, bitbucket or your own server, just push your commits there.
       
    59 Then send us the links to the commits/bookmarks in question!
       
    60 
       
    61 
       
    62 = How to let us know that you want your commits/patches to go into the official repository =
       
    63 
       
    64 Just send your patches (or links to them) to [/contact.html the development mailing list].
       
    65 
       
    66 Don't forget to add a short description (can be a copy of the commit message if it's explaining everything needed).
       
    67 
       
    68 *Note*: Please be aware that by sending in patches you grant unC0Rr (the project leader) *all rights* to your code (and any patents you may hold on it).
       
    69 That implies that your code *will be made public* under the *[http://www.gnu.org/licenses/old-licenses/gpl-2.0.en.html GNU GPL2]*.