Push one or more patches (defaulting to the first unapplied one) onto
the stack. The push operation allows patch reordering by commuting
them with the three-way merge algorithm. If there are conflicts while
pushing a patch, those conflicts are written to the work tree, and
the command halts. Conflicts raised during the push operation have to
be fixed and the git add --update command run (alternatively, you may
undo the conflicting push with stg undo).
The command also notifies when the patch becomes empty (fully merged
upstream) or is modified (three-way merged) by the push operation.
Push all the unapplied patches.
-n NUMBER, --number NUMBER
Push the specified number of patches.
With a negative number, push all but that many patches.
Push the patches in reverse order.
Push the patches, but don’t perform a merge. Instead, the
resulting tree will be identical to the tree that the patch
This can be useful when splitting a patch by first popping the
patch and creating a new patch with some of the changes. Pushing
the original patch with --set-tree will avoid conflicts and only
the remaining changes will be in the patch.
Keep the local changes.
Check for patches merged upstream.
This page is part of the stgit (Stacked Git) project. Information
about the project can be found at ⟨http://www.procode.org/stgit/⟩.
If you have a bug report for this manual page, see
⟨http://www.procode.org/stgit/⟩. This page was obtained from the
project's upstream Git repository ⟨http://repo.or.cz/stgit.git⟩ on
2017-03-13. If you discover any rendering problems in this HTML ver‐
sion of the page, or you believe there is a better or more up-to-date
source for the page, or you have corrections or improvements to the
information in this COLOPHON (which is not part of the original man‐
ual page), send a mail to email@example.com
StGit 03/13/2017 STG-PUSH(1)