Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-hash-object(1) [suse man page]

GIT-HASH-OBJECT(1)						    Git Manual							GIT-HASH-OBJECT(1)

NAME
git-hash-object - Compute object ID and optionally creates a blob from a file SYNOPSIS
git hash-object [-t <type>] [-w] [--path=<file>|--no-filters] [--stdin] [--] <file>... git hash-object [-t <type>] [-w] --stdin-paths [--no-filters] < <list-of-paths> DESCRIPTION
Computes the object ID value for an object with specified type with the contents of the named file (which can be outside of the work tree), and optionally writes the resulting object into the object database. Reports its object ID to its standard output. This is used by git cvsimport to update the index without modifying files in the work tree. When <type> is not specified, it defaults to "blob". OPTIONS
-t <type> Specify the type (default: "blob"). -w Actually write the object into the object database. --stdin Read the object from standard input instead of from a file. --stdin-paths Read file names from stdin instead of from the command-line. --path Hash object as it were located at the given path. The location of file does not directly influence on the hash value, but path is used to determine what git filters should be applied to the object before it can be placed to the object database, and, as result of applying filters, the actual blob put into the object database may differ from the given file. This option is mainly useful for hashing temporary files located outside of the working directory or files read from stdin. --no-filters Hash the contents as is, ignoring any input filter that would have been chosen by the attributes mechanism, including crlf conversion. If the file is read from standard input then this is always implied, unless the --path option is given. AUTHOR
Written by Junio C Hamano <gitster@pobox.com[1]> DOCUMENTATION
Documentation by David Greaves, 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-HASH-OBJECT(1)

Check Out this Related 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)
Man Page