git-lost-found(1) [suse man page]

GIT-LOST-FOUND(1)						    Git Manual							 GIT-LOST-FOUND(1)

NAME

       git-lost-found - Recover lost refs that luckily have not yet been pruned

SYNOPSIS

       git lost-found

DESCRIPTION

       NOTE: this command is deprecated. Use git-fsck(1) with the option --lost-found instead.

       Finds dangling commits and tags from the object database, and creates refs to them in the .git/lost-found/ directory. Commits and tags that
       dereference to commits are stored in .git/lost-found/commit, and other objects are stored in .git/lost-found/other.

OUTPUT

       Prints to standard output the object names and one-line descriptions of any commits or tags found.

EXAMPLE

       Suppose you run git tag -f and mistype the tag to overwrite. The ref to your tag is overwritten, but until you run git prune, the tag
       itself is still there.

	   .ft C
	   $ git lost-found
	   [1ef2b196d909eed523d4f3c9bf54b78cdd6843c6] GIT 0.99.9c
	   ...
	   .ft

       Also you can use gitk to browse how any tags found relate to each other.

	   .ft C
	   $ gitk $(cd .git/lost-found/commit && echo ??*)
	   .ft

       After making sure you know which the object is the tag you are looking for, you can reconnect it to your regular .git/refs hierarchy.

	   .ft C
	   $ git cat-file -t 1ef2b196
	   tag
	   $ git cat-file tag 1ef2b196
	   object fa41bbce8e38c67a218415de6cfa510c7e50032a
	   type commit
	   tag v0.99.9c
	   tagger Junio C Hamano <junkio@cox.net> 1131059594 -0800

	   GIT 0.99.9c

	   This contains the following changes from the "master" branch, since
	   ...
	   $ git update-ref refs/tags/not-lost-anymore 1ef2b196
	   $ git rev-parse not-lost-anymore
	   1ef2b196d909eed523d4f3c9bf54b78cdd6843c6
	   .ft

AUTHOR

       Written by Junio C Hamano <gitster@pobox.com[1]>

DOCUMENTATION

       Documentation by Junio C Hamano and the git-list <git@vger.kernel.org[2]>.

GIT

       Part of the git(1) suite

NOTES

	1. gitster@pobox.com
	   mailto:gitster@pobox.com

	2. git@vger.kernel.org
	   mailto:git@vger.kernel.org

Git 1.7.1							    07/05/2010							 GIT-LOST-FOUND(1)

GIT-REPLACE(1)							    Git Manual							    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.

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

SEE ALSO

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

AUTHOR

       Written by Christian Couder <chriscool@tuxfamily.org[1]> and Junio C Hamano <gitster@pobox.com[2]>, based on git tag by Kristian Hogsberg
       <krh@redhat.com[3]> and Carlos Rica <jasampler@gmail.com[4]>.

DOCUMENTATION

       Documentation by Christian Couder <chriscool@tuxfamily.org[1]> and the git-list <git@vger.kernel.org[5]>, based on git tag documentation.

GIT

       Part of the git(1) suite

NOTES

	1. chriscool@tuxfamily.org
	   mailto:chriscool@tuxfamily.org

	2. gitster@pobox.com
	   mailto:gitster@pobox.com

	3. krh@redhat.com
	   mailto:krh@redhat.com

	4. jasampler@gmail.com
	   mailto:jasampler@gmail.com

	5. git@vger.kernel.org
	   mailto:git@vger.kernel.org

Git 1.7.1							    07/05/2010							    GIT-REPLACE(1)