1git-replace(1) 2============== 3 4NAME 5---- 6git-replace - Create, list, delete refs to replace objects 7 8SYNOPSIS 9-------- 10[verse] 11'git replace' [-f] <object> <replacement> 12'git replace' -d <object>... 13'git replace' -l [<pattern>] 14 15DESCRIPTION 16----------- 17Adds a 'replace' reference in `.git/refs/replace/` 18 19The name of the 'replace' reference is the SHA1 of the object that is 20replaced. The content of the replace reference is the SHA1 of the 21replacement object. 22 23Unless `-f` is given, the replace reference must not yet exist in 24`.git/refs/replace/` directory. 25 26OPTIONS 27------- 28-f:: 29 If an existing replace ref for the same object exists, it will 30 be overwritten (instead of failing). 31 32-d:: 33 Delete existing replace refs for the given objects. 34 35-l <pattern>:: 36 List replace refs for objects that match the given pattern (or 37 all if no pattern is given). 38 Typing "git replace" without arguments, also lists all replace 39 refs. 40 41BUGS 42---- 43Comparing blobs or trees that have been replaced with those that 44replace them will not work properly. And using 'git reset --hard' to 45go back to a replaced commit will move the branch to the replacement 46commit instead of the replaced commit. 47 48There may be other problems when using 'git rev-list' related to 49pending objects. And of course things may break if an object of one 50type is replaced by an object of another type (for example a blob 51replaced by a commit). 52 53SEE ALSO 54-------- 55linkgit:git-tag[1] 56linkgit:git-branch[1] 57 58Author 59------ 60Written by Christian Couder <chriscool@tuxfamily.org> and Junio C 61Hamano <gitster@pobox.com>, based on 'git tag' by Kristian Hogsberg 62<krh@redhat.com> and Carlos Rica <jasampler@gmail.com>. 63 64Documentation 65-------------- 66Documentation by Christian Couder <chriscool@tuxfamily.org> and the 67git-list <git@vger.kernel.org>, based on 'git tag' documentation. 68 69GIT 70--- 71Part of the linkgit:git[1] suite