table of contents
other versions
- wheezy 1:1.7.10.4-1+wheezy3
- wheezy-backports 1:1.9.1-1~bpo70+2
- jessie 1:2.1.4-2.1+deb8u2
- jessie-backports 1:2.11.0-3~bpo8+1
- testing 1:2.11.0-3
- unstable 1:2.11.0-4
- experimental 1:2.13.1+next.20170610-1
GIT-REPLACE(1) | Git Manual | GIT-REPLACE(1) |
NAME¶
git-replace - Create, list, delete refs to replace objectsSYNOPSIS¶
git replace [-f] <object> <replacement> git replace -d <object>... git replace [--format=<format>] [-l [<pattern>]]
DESCRIPTION¶
Adds a replace reference in refs/replace/ namespace.$ git --no-replace-objects cat-file commit foo
$ git cat-file commit foo
OPTIONS¶
-f, --forceIf an existing replace ref for the same object
exists, it will be overwritten (instead of failing).
-d, --delete
Delete existing replace refs for the given
objects.
-l <pattern>, --list <pattern>
List replace refs for objects that match the
given pattern (or all if no pattern is given). Typing "git replace"
without arguments, also lists all replace refs.
--format=<format>
When listing, use the specified
<format>, which can be one of short, medium and
long. When omitted, the format defaults to short.
FORMATS¶
The following format are available:•
short: <replaced sha1>
•
medium: <replaced sha1> → <replacement sha1>
•
long: <replaced sha1> (<replaced type>) →
<replacement sha1> (<replacement type>)
CREATING REPLACEMENT OBJECTS¶
git-filter-branch(1), git-hash-object(1) and git-rebase(1), among other git commands, can be used to create replacement objects from existing objects.BUGS¶
Comparing blobs or trees that have been replaced with those that replace them will not work properly. And using git reset --hard to go back to a replaced commit will move the branch to the replacement commit instead of the replaced commit.SEE ALSO¶
git-hash-object(1) git-filter-branch(1) git-rebase(1) git-tag(1) git-branch(1) git(1)GIT¶
Part of the git(1) suite04/08/2014 | Git 1.9.1 |