ContributingCode.wiki
changeset 870 55e67d58d19e
parent 798 30c5f1ebd552
child 1282 4d2674ab4844
equal deleted inserted replaced
869:a09b1abfe5e8 870:55e67d58d19e
    40 
    40 
    41 *In order for us to be able which bugfixes/features of you we merge into the official repository, you should put each in a separate _unnamed branch_ as described above.*
    41 *In order for us to be able which bugfixes/features of you we merge into the official repository, you should put each in a separate _unnamed branch_ as described above.*
    42 
    42 
    43 Make sure that the first commit of each bugfix/feature commit set is based on a commit from the official repository, that way your bugfixes/features will not depend on the commits of each other and can be merged into official individually, as needed.
    43 Make sure that the first commit of each bugfix/feature commit set is based on a commit from the official repository, that way your bugfixes/features will not depend on the commits of each other and can be merged into official individually, as needed.
    44 
    44 
    45 That means: *Before you start writing code towards a new bugfix/feature, make sure to {{{hg update}}} to a revision from the official repository.*
    45 That means: *Before you start writing code towards a new bugfix/feature, make sure to {{{hg update -r}}} to a revision from the official repository.*
    46 
    46 
    47 
    47 
    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 [https://hg.hedgewars.org/hw-example-clone/graph HERE]*
    50 *You can see example of how unnamed branches and bookmarks are used best [https://hg.hedgewars.org/hw-example-clone/graph HERE]*