2023-11-24 11:10:31 +00:00
|
|
|
git-replay(1)
|
|
|
|
=============
|
|
|
|
|
|
|
|
NAME
|
|
|
|
----
|
|
|
|
git-replay - EXPERIMENTAL: Replay commits on a new base, works with bare repos too
|
|
|
|
|
|
|
|
|
|
|
|
SYNOPSIS
|
|
|
|
--------
|
|
|
|
[verse]
|
|
|
|
(EXPERIMENTAL!) 'git replay' --onto <newbase> <oldbase> <branch>
|
|
|
|
|
|
|
|
DESCRIPTION
|
|
|
|
-----------
|
|
|
|
|
|
|
|
Takes a range of commits, specified by <oldbase> and <branch>, and
|
2023-11-24 11:10:39 +00:00
|
|
|
replays them onto a new location (see `--onto` option below). Leaves
|
|
|
|
the working tree and the index untouched, and updates no references.
|
|
|
|
The output of this command is meant to be used as input to
|
|
|
|
`git update-ref --stdin`, which would update the relevant branches.
|
2023-11-24 11:10:31 +00:00
|
|
|
|
|
|
|
THIS COMMAND IS EXPERIMENTAL. THE BEHAVIOR MAY CHANGE.
|
|
|
|
|
|
|
|
OPTIONS
|
|
|
|
-------
|
|
|
|
|
|
|
|
--onto <newbase>::
|
|
|
|
Starting point at which to create the new commits. May be any
|
|
|
|
valid commit, and not just an existing branch name.
|
|
|
|
|
|
|
|
EXIT STATUS
|
|
|
|
-----------
|
|
|
|
|
|
|
|
For a successful, non-conflicted replay, the exit status is 0. When
|
|
|
|
the replay has conflicts, the exit status is 1. If the replay is not
|
|
|
|
able to complete (or start) due to some kind of error, the exit status
|
|
|
|
is something other than 0 or 1.
|
|
|
|
|
|
|
|
GIT
|
|
|
|
---
|
|
|
|
Part of the linkgit:git[1] suite
|