Submitting Patches - Revision history

Dirk: to get a patch file, you need to redirect the output of hg export ...

2010-05-03T18:03:27Z

to get a patch file, you need to redirect the output of hg export ...

LWC: Added title and fixed typo

2010-04-05T10:32:34Z

Added title and fixed typo

LWC: GUI equivalence

2010-04-05T10:31:54Z

GUI equivalence

Dirk: mention diff -u as an alternative to hg export

2010-03-13T17:25:56Z

mention diff -u as an alternative to hg export

Dirk: more on hg export

2010-02-10T13:26:59Z

Dirk: added a link to Tags and Branches

2009-05-30T17:35:33Z

added a link to Tags and Branches

Dirk: added link to bugtracker

2009-04-19T16:38:10Z

added link to bugtracker

Dirk: hg export tip

2009-04-12T18:44:35Z

hg export tip

Dirk: Quick guide on how to submit a patch

2009-03-13T08:59:03Z

Quick guide on how to submit a patch

New page

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

* check out the source code
* make the necessary changes to the source
* 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
** 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 [http://eight.pairlist.net/mailman/admindb/geeklog-devel geeklog-devel] mailing list (if the patch is really huge, you may want to upload it somewhere and only send the URL)

Thank you!

[[Category:Development]]

@@ Line 7: / Line 7: @@
 * Exporting:
 ** 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>
+*** to export the latest changeset from your repository, simply use <pre>hg export tip > patch.diff</pre>
 *** The TortoiseHg GUI equivalence is: '''Hg Repository Explorer=>choose Changeset=>Export Patch'''
 * 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 (Note: while <tt>hg export</tt> can export multiple changesets into one file, the equivalent <tt>hg import</tt> currently only accepts one changeset per file, so we're asking for separate files.)

@@ Line 1: / Line 1: @@
 If you want to submit a patch for Geeklog, please check out the current development version from our [[Using Mercurial|Mercurial]] repository. You can also submit patches against released versions by checking out that version's code using the <tt>..._stable</tt> [[Tags and Branches|tag]].
 * check out the source code
 * make the necessary changes to the source
@@ Line 7: / Line 8: @@
 ** 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>
-*** The TortoiseHg GUI equivalence is: '''Hd Repository Explorer=>choose Changeset=>Export Patch'''
+*** The TortoiseHg GUI equivalence is: '''Hg Repository Explorer=>choose Changeset=>Export Patch'''
 * 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 (Note: while <tt>hg export</tt> can export multiple changesets into one file, the equivalent <tt>hg import</tt> currently only accepts one changeset per file, so we're asking for separate files.)
 * Diff files:

@@ Line 4: / Line 4: @@
 * make the necessary changes to the source
 * 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
+* Exporting:
-** to export the latest changeset from your repository, simply use <pre>hg export tip</pre>
+** export the changeset using <tt>hg export REV</tt> where <tt>REV</tt> is the revision number of the changeset
-** 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 (Note: while <tt>hg export</tt> can export multiple changesets into one file, the equivalent <tt>hg import</tt> currently only accepts one changeset per file, so we're asking for separate files.)
+*** to export the latest changeset from your repository, simply use <pre>hg export tip</pre>
-* if you are '''not''' using <tt>hg export</tt> please send ''unified'' diff files and make sure you list the files in the correct order, i.e. <pre>diff -u original-file modified-file > patch.diff</pre>
+*** The TortoiseHg GUI equivalence is: '''Hd Repository Explorer=>choose Changeset=>Export Patch'''
 * add the patch (or zipped/gzipped set of patches) as an attachment to the bug or feature request in question on our [http://project.geeklog.net/tracking/ bugtracker]
 ** if there is no bug or feature request for your patch, send the patch (with an explanation) to the [http://eight.pairlist.net/mailman/admindb/geeklog-devel geeklog-devel] mailing list (if the patch is really huge, you may want to upload it somewhere and only send the URL)
 Thank you!
 == diff vs. hg export ==
@@ Line 19: / Line 22: @@
 * include the checkin comment
 * give proper attribution to the person who created the patch (i.e. '''you''')
 [[Category:Development]]

@@ Line 7: / Line 7: @@
 ** 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 (Note: while <tt>hg export</tt> can export multiple changesets into one file, the equivalent <tt>hg import</tt> currently only accepts one changeset per file, so we're asking for separate files.)
 * add the patch (or zipped/gzipped set of patches) as an attachment to the bug or feature request in question on our [http://project.geeklog.net/tracking/ bugtracker]
 ** if there is no bug or feature request for your patch, send the patch (with an explanation) to the [http://eight.pairlist.net/mailman/admindb/geeklog-devel geeklog-devel] mailing list (if the patch is really huge, you may want to upload it somewhere and only send the URL)

← Older revision		Revision as of 17:35, 30 May 2009
Line 1:		Line 1:
−	If you want to submit a patch for Geeklog, please check out the current development version from our [[Using Mercurial\|Mercurial]] repository. You can also submit patches against released versions by checking out that version's code using the <tt>..._stable</tt> tag.	+	If you want to submit a patch for Geeklog, please check out the current development version from our [[Using Mercurial\|Mercurial]] repository. You can also submit patches against released versions by checking out that version's code using the <tt>..._stable</tt> [[Tags and Branches\|tag]].

	* check out the source code		* check out the source code