git-replace man page on OpenBSD

Man page or keyword search:  
man Server   11362 pages
apropos Keyword Search (all sections)
Output format
OpenBSD logo
[printable version]



GIT-REPLACE(1)					   GIT-REPLACE(1)

NAME
       git-replace - Create, list, delete refs to replace objects

SYNOPSIS
       git replace [-f] <object> <replacement>
       git replace -d <object>...
       git replace -l [<pattern>]

DESCRIPTION
       Adds a replace reference in .git/refs/replace/

       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 in
       .git/refs/replace/ directory.

       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:

       .ft C
       $ git --no-replace-objects cat-file commit foo
       .ft

       shows information about commit foo, while:

       .ft C
       $ git cat-file commit foo
       .ft

       shows information about commit bar.

								1

GIT-REPLACE(1)					   GIT-REPLACE(1)

       The  GIT_NO_REPLACE_OBJECTS  environment variable can be set to achieve
       the same effect as the --no-replace-objects option.

OPTIONS
       -f     If an existing replace ref for the same object exists,  it  will
	      be overwritten (instead of failing).

       -d     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	 argu-
	      ments, also lists all replace refs.

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

SEE ALSO
       git-tag(1) git-branch(1) git(1)

AUTHOR
       Written	    by	    Christian	  Couder     <chriscool@tuxfamily.org:
       mailto:chriscool@tuxfamily.org> and Junio C Hamano  <gitster@pobox.com:
       mailto:gitster@pobox.com>,  based  on  git  tag	by  Kristian  Hogsberg
       <krh@redhat.com:	 mailto:krh@redhat.com>	 and   Carlos	Rica   <jasam-
       pler@gmail.com: mailto:jasampler@gmail.com>.

DOCUMENTATION
       Documentation	by    Christian	   Couder    <chriscool@tuxfamily.org:
       mailto:chriscool@tuxfamily.org> and the git-list	 <git@vger.kernel.org:
       mailto:git@vger.kernel.org>, based on git tag documentation.

GIT
       Part of the git(1) suite

								2

[top]

List of man pages available for OpenBSD

Copyright (c) for man pages and the logo by the respective OS vendor.

For those who want to learn more, the polarhome community provides shell access and support.

[legal] [privacy] [GNU] [policy] [cookies] [netiquette] [sponsors] [FAQ]
Tweet
Polarhome, production since 1999.
Member of Polarhome portal.
Based on Fawad Halim's script.
....................................................................
Vote for polarhome
Free Shell Accounts :: the biggest list on the net