Differences

This shows you the differences between two versions of the page.

--- writeandsubmitpatch [2010/02/08 12:49] – created glaubitz
+++ writeandsubmitpatch [2013/05/16 11:39] – [Checking out the git repository] glaubitz
@@ Line 9: / Line 9: @@
     * checking out the git repository
     * creating a git branch for your patches
-    * editing the source and committing the changes
+    * editing the source and committing the changes in your branch
-      in your branch
     * creating a patch in .diff format
     * sending the patch to the mailing list
@@ Line 16: / Line 15: @@
 All these tasks can be performed with git, except, of course, you
 still need an editor to make your changes to the source.
+===== Preparing git =====
+Make sure that your environment variables set your email address correctly (environment variable //EMAIL//).
+If you do not want to use the same address for //git// as your regular address in the Unix system,
+then just set the environment variables for //git//. For example, in your .bashrc, add:
+<code>
+export GIT_AUTHOR_NAME="Your Name"
+export GIT_AUTHOR_EMAIL="Yourmail@Yourdomain"
+</code>
+This will make sure that all your patches are signed with your name as author and your email
+address. It is important to use your real name here and provide a working email address. Otherwise
+we cannot likely accept your patches.
 ===== Checking out the git repository =====
@@ Line 23: / Line 37: @@
 <code>
-git clone git://z6.physik.fu-berlin.de/linux-minidisc
+git clone git://z6.physik.fu-berlin.de/linux-minidisc.git
 </code>
@@ Line 115: / Line 129: @@
 some mail clients may mess up the format of the patch,
 it's recommended to use the built-in command //git send-email//
-to send the patches in to the mailing list:
+to send the patches in to the mailing list (please see also the appropriate manpage: [[http://www.kernel.org/pub/software/scm/git/docs/git-send-email.html]]):
 <code>