Historically (5 Nov 2005 v0.99.9-46-g28ffb89) the git-format-patch used 'origin' as the upstream branch name. This is now used to name the remote. Use the more modern 'master' as the branch name. Signed-off-by: Philip Oakley <philipoakley@xxxxxxx> --- I noticed this while cross-checking details for updating the guide Documentation/(git)everyday.txt -- Philip Documentation/git-format-patch.txt | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/git-format-patch.txt b/Documentation/git-format-patch.txt index c0fd470..b0f041f 100644 --- a/Documentation/git-format-patch.txt +++ b/Documentation/git-format-patch.txt @@ -523,25 +523,25 @@ $ git format-patch -k --stdout R1..R2 | git am -3 -k ------------ * Extract all commits which are in the current branch but not in the -origin branch: +master branch: + ------------ -$ git format-patch origin +$ git format-patch master ------------ + For each commit a separate file is created in the current directory. -* Extract all commits that lead to 'origin' since the inception of the +* Extract all commits that lead to 'master' since the inception of the project: + ------------ -$ git format-patch --root origin +$ git format-patch --root master ------------ * The same as the previous one: + ------------ -$ git format-patch -M -B origin +$ git format-patch -M -B master ------------ + Additionally, it detects and handles renames and complete rewrites -- 1.9.4.msysgit.0 -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html