Fork us on GitHub Follow us on Facebook Follow us on Twitter

Changes between Version 11 and Version 12 of HowToContribute


Ignore:
Timestamp:
2011-04-02T13:21:06Z (8 years ago)
Author:
Jakub Jermář
Comment:

Mention the possibility to submit a merge directive.

Legend:

Unmodified
Added
Removed
Modified
  • HowToContribute

    v11 v12  
    2828 * Choose a [http://trac.helenos.org/wiki/BazaarWorkflow#Youridentity Bazaar identity] and include it in the message so we can correctly attribute you with `--author`. This is important as not everybody wants their real e-mail address to appear in the commit log.
    2929
    30 Alternatively you can provide us with a pointer to a public Bazaar branch (e.g. on [https://launchpad.net/ Launchpad]) from where we can pick the changes.
     30Alternatively you can provide us with a pointer to a public Bazaar branch (e.g. on [https://launchpad.net/ Launchpad]) from where we can pick the changes. In case you maintain a local branch with your changes and don't want to publish it, we can still merge from it using a Bazaar merge directive. A merge directive can be viewed as a better text patch which carries all the history and change information of your local branch while still being human readable. Once your local branch is ready to be merged, the merge directive can be created as follows:
     31
     32{{{
     33$ bzr send -o my_merge.directive
     34}}}
     35
     36Then send a brief message describing the change to our mailing list and attach ```my_merge.directive``` to it.
    3137
    3238== Compiling the system ==