Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>As in "<a href="https://stackoverflow.com/questions/9078820/create-a-single-patch-between-two-tags-with-multiple-commits-between-them">Create a single patch between two tags with multiple commits between them</a>", you could create a single path between v3.0.36. and 3.0.38, specifying the subdirectory which is of interest to you within one repo.</p> <pre><code>git diff tag1 tag2 -- /path/to/subdir &gt; the-patch.diff </code></pre> <p>The idea is, you can apply a diff to another repo.</p> <p>Regarding GitHub, the same mechanism apply with <a href="https://help.github.com/articles/using-pull-requests/" rel="nofollow noreferrer">pull requests</a>: once you have patched locally, you can push to our GitHub repo which should be a <strong><a href="https://help.github.com/articles/fork-a-repo" rel="nofollow noreferrer">fork</a></strong>, and then make a pull request.</p> <hr> <p>As <a href="https://stackoverflow.com/users/410126/fork0">fork0</a> comments, <code>git diff</code> would loose the comments associated with the commit.<br> <code>git format-patch</code> is a better solution (and I upvoted fork's <a href="https://stackoverflow.com/a/11615326/6309">answer</a>).<br> I would consider <code>cherry-pick</code> only if you are aware of <a href="https://stackoverflow.com/a/881112/6309">its limitation</a>.</p> <hr> <p>As <a href="https://github.com/biergaizi/AIR-Kernel_ICS/commit/27aec2107c6c9f0aea46ebc011ee17357ee8e784" rel="nofollow noreferrer">commit like this one</a> is the result of a pull request done by gregkh, accepted by edoko.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload