aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorDaniel Stenberg <daniel@haxx.se>2010-04-12 11:20:00 +0200
committerDaniel Stenberg <daniel@haxx.se>2010-04-12 11:20:00 +0200
commit4f9b47de8c3fdd530921a43aa1e67735f0b8b461 (patch)
tree6716f9b40ab2757689a56d2e6953f55ec52c3036 /docs
parentf9db721c1c7723517be72a86b586f64b8af772b1 (diff)
Added text for How To Make a Patch with git
Diffstat (limited to 'docs')
-rw-r--r--docs/CONTRIBUTE23
1 files changed, 22 insertions, 1 deletions
diff --git a/docs/CONTRIBUTE b/docs/CONTRIBUTE
index 633f131e1..c6ecee785 100644
--- a/docs/CONTRIBUTE
+++ b/docs/CONTRIBUTE
@@ -187,7 +187,28 @@
3.2 How To Make a Patch with git
- TODO
+ You need to first checkout the respository:
+
+ git clone git://github.com/bagder/curl.git
+
+ You then proceed and edit all the files you like and you commit them to your
+ local repository:
+
+ git commit [file]
+
+ As usual, group your commits so that you commit all changes that at once that
+ constitutes a logical change.
+
+ Once you have done all your commits and you're happy with what you see, you
+ can make patches out of your changes that are suitable for mailing:
+
+ git format-patch remotes/origin/master
+
+ This creates files in your local directory named NNNN-[name].patch for each
+ commit.
+
+ Now send those patches off to the curl-library list. You can of course opt to
+ do that with the 'get send-email' command.
3.3 How To Make a Patch without git