From 62b97446d0d3e0161d8d5ba54d9e4536cff99437 Mon Sep 17 00:00:00 2001 From: Mattias Andrée Date: Fri, 16 Aug 2013 03:09:57 +0200 Subject: creating a patch MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Signed-off-by: Mattias Andrée --- using-git.texinfo | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) (limited to 'using-git.texinfo') diff --git a/using-git.texinfo b/using-git.texinfo index ce906d3..fe40278 100644 --- a/using-git.texinfo +++ b/using-git.texinfo @@ -472,6 +472,7 @@ the files and make a new commit. @menu * Cloning a repository:: +* Submitting patches:: @end menu @@ -497,6 +498,30 @@ upstream repository, use +@node Submitting patches +@section Submitting patches + +The best way to create a patch is with Git's +@command{format-patch} command. Assuming +you began from @code{upstream/master}: + +@example +git format-patch upstream/master +@end example + +This command with create a patch whose name +will be printed by @command{git format-patch}. + +Creating a patch this way will keep track +of the commit messages, and the individual +commits. Another advantage with it is that +it can easily be submitted to a mailing list, +which the common way for large projects for +accepting patches. + + + + @node GNU Free Documentation License @appendix GNU Free Documentation License @include fdl.texinfo -- cgit v1.2.3-70-g09d2