[giimote:202] [wiki.giimote] push by - Updated wiki article for mercurial on 2010-05-25 14:47 GMT

[gii...@googlecode.com]

Revision: 48aae4580f
Author: samwhited
Date: Tue May 25 07:47:57 2010
Log: Updated wiki article for mercurial
http://code.google.com/p/giimote/source/detail?repo=wiki&r=48aae4580f

Modified:
/CreatingPatches.wiki

=======================================
--- /CreatingPatches.wiki Mon May 24 21:55:57 2010
+++ /CreatingPatches.wiki Tue May 25 07:47:57 2010
@@ -1,26 +1,26 @@
-#summary Instructions for creating and submitting a subversion patch
-#labels Phase-Implementation,Deprecated
+#summary Instructions for creating and submitting a mercurial patch
+#labels Phase-Implementation

= Introduction =

-GiiMote is an open source project and user contributions are welcome in
the form of patches. Patch files are small, portable, ".diff" files which
describe all of the changes the developer has made to the source code (the
*diff*-erences). These files can then be reviewed and checked in to the
repository.
+GiiMote is an open source project and user contributions are welcome in
the form of patches. Patch files are small, portable, ".diff" files which
describe all of the changes the developer has made to the source code.
These files can then be reviewed and merged with the project. If you do not
have access to the repository you should use patches to submit your changes.


= Creating a patch =

-To create a patch first [BuildDocumentation download and build] GiiMote.
After you are sure GiiMote compiles correctly make and test your changes.
Once your changes compile correctly, are bug-free, and follow the
appropriate [CodingStyles coding styles] you can navigate to the root
directory of the project and execute the following command to see a list of
all modified files:
+To create a patch first [BuildDocumentation download and build] GiiMote.
After you are sure GiiMote compiles correctly make and test your changes.
Once your changes compile correctly, are bug-free, and follow the
appropriate [CodingStyles coding conventions] you can navigate to the root
directory of the project and execute the following command to see a list of
all changes:

{{{
-svn status
+hg log
}}}

-To create the actual patch file you can then run:
+To create the actual patch you can then run:

{{{
-svn diff > patch_file.diff
+hg export 2 > changeset2.diff
}}}

-Make sure you are in the root directory (not trunk, but the directory
containing it) when you create your diff file and that you give the file a
descriptive name.
+This would export changeset 2. Make sure you are in the root directory
when you create your diff file and that you give the file a descriptive
name.


= Submitting a patch =
@@ -31,4 +31,3 @@
= Links =

* [http://code.google.com/p/giimote/issues/list Issues List]
- * [http://svnbook.red-bean.com/en/1.5/svn.ref.svn.c.diff.html svn diff]