Setup and Config
Getting and Creating Projects
Branching and Merging
Sharing and Updating Projects
Inspection and Comparison
- 2.5.2 → 2.6.3 no changes
- 2.5.1 08/28/15
- 2.5.0 07/27/15
- 2.4.10 no changes
- 2.4.9 09/04/15
- 2.4.1 → 2.4.8 no changes
- 2.4.0 04/30/15
- 2.3.9 09/04/15
- 2.1.1 → 2.3.8 no changes
- 2.1.0 08/15/14
- 1.9.1 → 2.0.5 no changes
- 1.9.0 02/14/14
- 126.96.36.199 → 188.8.131.52 no changes
- 1.8.5 11/27/13
- 184.108.40.206 → 220.127.116.11 no changes
- 18.104.22.168 04/26/13
- 22.214.171.124 04/07/13
- 126.96.36.199 → 188.8.131.52 no changes
- 184.108.40.206 09/18/12
- 1.7.12 08/20/12
- 220.127.116.11 no changes
- 18.104.22.168 09/11/12
git-replace(1) Manual Page
git-replace - Create, list, delete refs to replace objects
git replace [-f] <object> <replacement> git replace -d <object>... git replace -l [<pattern>]
Adds a replace reference in refs/replace/ namespace.
The name of the replace reference is the SHA1 of the object that is replaced. The content of the replace reference is the SHA1 of the replacement object.
Unless -f is given, the replace reference must not yet exist.
Replacement references will be used by default by all git commands except those doing reachability traversal (prune, pack transfer and fsck).
It is possible to disable use of replacement references for any command using the --no-replace-objects option just after git.
For example if commit foo has been replaced by commit bar:
$ git --no-replace-objects cat-file commit foo
shows information about commit foo, while:
$ git cat-file commit foo
shows information about commit bar.
The GIT_NO_REPLACE_OBJECTS environment variable can be set to achieve the same effect as the --no-replace-objects option.
If an existing replace ref for the same object exists, it will be overwritten (instead of failing).
Delete existing replace refs for the given objects.
- -l <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.
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.
There may be other problems when using git rev-list related to pending objects. And of course things may break if an object of one type is replaced by an object of another type (for example a blob replaced by a commit).
Part of the git(1) suite