diff options
| author | Mattias Andrée <maandree@operamail.com> | 2013-08-16 03:09:57 +0200 |
|---|---|---|
| committer | Mattias Andrée <maandree@operamail.com> | 2013-08-16 03:09:57 +0200 |
| commit | 62b97446d0d3e0161d8d5ba54d9e4536cff99437 (patch) | |
| tree | fa4ae52990b26275906f7066ffd0b32313ed52fa | |
| parent | cloning repositories (diff) | |
| download | using-git-62b97446d0d3e0161d8d5ba54d9e4536cff99437.tar.gz using-git-62b97446d0d3e0161d8d5ba54d9e4536cff99437.tar.bz2 using-git-62b97446d0d3e0161d8d5ba54d9e4536cff99437.tar.xz | |
creating a patch
Signed-off-by: Mattias Andrée <maandree@operamail.com>
| -rw-r--r-- | using-git.texinfo | 25 |
1 files changed, 25 insertions, 0 deletions
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 |