In git, how do I create a single patch for the last 2+ revisions?
I would like to create a patch for the last 2 revisions.
git format-patch -2
gives me 2 patch files, one for each revision
git format-patch HEAD~2..HEAD
gives the same thing.
git format-patch -1 HEAD~2..HEAD
gives a single file, but only contains changes for the last revision.
Is there any way to do this in git?
git diff HEAD~2..HEAD > my-patch.diff
It won't have any of format-patch's per-commit metadata, though.
Use the --stdout option and then cat it to a file.
Like so:
git format-patch HEAD~2..HEAD --stdout > changes.patch
This will keep the per-commit metadata.
With Git 2.20 (Q4 2018) and more, you now have:
-
git format-patch --interdiff
. -
git format-patch --rangediff
.
Both are helping to explain the difference between this version and the previous attempt in the cover letter (or after the tree-dashes as a comment).
format-patch
: allow--interdiff
/--rangediff
to apply to a lone-patchWhen submitting a revised version of a patch or series, it can be helpful (to reviewers) to include a summary of changes since the previous attempt in the form of an interdiff, typically in the cover letter.
However, it is occasionally useful, despite making for a noisy read, to insert an interdiff or a rangediff into the commentary section of the lone patch of a 1-patch series.
See commit ee6cbf7, commit 3fcc7a2, commit 3b02641, commit 5ac290f, commit 126facf, commit fa5b7ea (22 Jul 2018) by Eric Sunshine (sunshineco
).
(Merged by Junio C Hamano -- gitster
-- in commit 688cb1c, 17 Sep 2018)
Therefore, extend "
git format-patch --interdiff=<prev>
" to insert an interdiff into the commentary section of a lone patch rather than requiring a cover letter.
The interdiff is indented to avoid confusinggit-am
and human readers into considering it part of the patch proper.
See commit 40ce416, commit 8631bf1, commit 4ee9968, commit 2e6fd71, commit 31e2617, commit 73a834e, commit 2566865, commit 87f1b2d (22 Jul 2018) by Eric Sunshine (sunshineco
).
(Merged by Junio C Hamano -- gitster
-- in commit 881c019, 17 Sep 2018)
Therefore, extend "
git format-patch --range-diff=<refspec>
" to insert arange-diff
into the commentary section of a lone patch rather than requiring a cover letter.