Difference between revisions of "Submitting Patches"

From GeeklogWiki
Jump to: navigation, search
(Quick guide on how to submit a patch)
 
(hg export tip)
Line 5: Line 5:
 
* commit changes into your local repository
 
* commit changes into your local repository
 
* export the changeset using <tt>hg export REV</tt> where <tt>REV</tt> is the revision number of the changeset
 
* export the changeset using <tt>hg export REV</tt> where <tt>REV</tt> is the revision number of the changeset
 +
** to export the latest changeset from your repository, simply use <pre>hg export tip</pre>
 
** if your patch consists of more than one changeset, please export them individually into separate files with consecutive numbers so we know in which order they need to be applied
 
** if your patch consists of more than one changeset, please export them individually into separate files with consecutive numbers so we know in which order they need to be applied
 
* add the patch (or zipped/gzipped set of patches) as an attachment to the bug or feature request in question
 
* add the patch (or zipped/gzipped set of patches) as an attachment to the bug or feature request in question

Revision as of 18:44, 12 April 2009

If you want to submit a patch for Geeklog, please check out the current development version from our Mercurial repository. You can also submit patches against released versions by checking out that version's code using the ..._stable tag.

  • check out the source code
  • make the necessary changes to the source
  • commit changes into your local repository
  • export the changeset using hg export REV where REV is the revision number of the changeset
    • to export the latest changeset from your repository, simply use
      hg export tip
    • if your patch consists of more than one changeset, please export them individually into separate files with consecutive numbers so we know in which order they need to be applied
  • add the patch (or zipped/gzipped set of patches) as an attachment to the bug or feature request in question
    • if there is no bug or feature request for your patch, send the patch (with an explanation) to the geeklog-devel mailing list (if the patch is really huge, you may want to upload it somewhere and only send the URL)

Thank you!