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 export your changes so that we can use them = |
53 = How to export your changes so that we can use them = |
54 |
54 |
55 TODO: diffs, exported patches, public repo clone, etc. |
55 == Public Repository == |
|
56 If you setup a public repository e.g. at github, bitbucket or on your own server, just push your commits there. |
|
57 Then send us the links to the commits/bookmarks that you want to go into the official repository! |
56 |
58 |
57 == Public Repository == |
59 == Export mercurial commits == |
58 If you setup a public repository e.g. at github, bitbucket or your own server, just push your commits there. |
60 With {{{hg export --git -r commitid1 -rcommitid2 ... > my.patch}}} you can export the commits specified to a patch file. |
59 Then send us the links to the commits/bookmarks in question! |
61 |
|
62 Note: the {{{--git}}} argument is used, so that binary file changes (e.g. changed pictures), are included in the export. |
|
63 |
|
64 == Creating a file containing the code differences == |
|
65 You can use the {{{diff}}} command (if available on your platform) to output the differences between e.g. the original code and yours. |
|
66 Save that into a file and send it to us. |
|
67 Note: Don't forget to also send binary files, so pictures/etc. that you changed - since usually {{{diff}}} will only cover text changes! |
|
68 |
|
69 |
|
70 |
|
71 If you have a mercurial clone of the official repository but you don't want to locally commit your changes for some reason, you can use use {{{hg diff --git > my.diff}}} to generate a diff file containing changes to code and binary files. |
60 |
72 |
61 |
73 |
62 = How to let us know that you want your commits/patches to go into the official repository = |
74 = How to let us know that you want your commits/patches to go into the official repository = |
63 |
75 |
64 Just send your patches (or links to them) to [/contact.html the development mailing list]. |
76 Just send your patches (or links to them) to [/contact.html the development mailing list]. |