Mac Developer Library Developer


This manual page is part of Xcode Tools version 5.0

To obtain these tools:

If you are running a version of Xcode Tools other than 5.0, view the documentation locally:

  • In Xcode

  • In Terminal, using the man(1) command

Reading manual pages

Manual pages are intended as a quick reference for people who already understand a technology.

  • To learn how the manual is organized or to learn about command syntax, read the manual page for manpages(5).

  • For more information about this technology, look for other documentation in the Apple Developer Library.

  • For general information about writing shell scripts, read Shell Scripting Primer.

GIT-REPLACE(1)                                   Git Manual                                   GIT-REPLACE(1)

       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 SHA-1 of the object that is replaced. The content of the
       replace reference is the SHA-1 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

           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).

       git-tag(1) git-branch(1) git(1)

       Part of the git(1) suite

Git 1.8.3                                        05/24/2013                                   GIT-REPLACE(1)

Reporting Problems

The way to report a problem with this manual page depends on the type of problem:

Content errors
Report errors in the content of this documentation with the feedback links below.
Bug reports
Report bugs in the functionality of the described tool or API through Bug Reporter.
Formatting problems
Report formatting mistakes in the online version of these pages with the feedback links below.