Linux and UNIX Man Pages

Linux & Unix Commands - Search Man Pages

git-var(1) [debian man page]

GIT-VAR(1)							    Git Manual								GIT-VAR(1)

NAME
git-var - Show a git logical variable SYNOPSIS
git var ( -l | <variable> ) DESCRIPTION
Prints a git logical variable. OPTIONS
-l Cause the logical variables to be listed. In addition, all the variables of the git configuration file .git/config are listed as well. (However, the configuration variables listing functionality is deprecated in favor of git config -l.) EXAMPLE
$ git var GIT_AUTHOR_IDENT Eric W. Biederman <ebiederm@lnxi.com> 1121223278 -0600 VARIABLES
GIT_AUTHOR_IDENT The author of a piece of code. GIT_COMMITTER_IDENT The person who put a piece of code into git. GIT_EDITOR Text editor for use by git commands. The value is meant to be interpreted by the shell when it is used. Examples: ~/bin/vi, $SOME_ENVIRONMENT_VARIABLE, "C:Program FilesVimgvim.exe" --nofork. The order of preference is the $GIT_EDITOR environment variable, then core.editor configuration, then $VISUAL, then $EDITOR, and then finally vi. GIT_PAGER Text viewer for use by git commands (e.g., less). The value is meant to be interpreted by the shell. The order of preference is the $GIT_PAGER environment variable, then core.pager configuration, then $PAGER, and then finally less. DIAGNOSTICS
You don't exist. Go away! The passwd(5) gecos field couldn't be read Your parents must have hated you! The passwd(5) gecos field is longer than a giant static buffer. Your sysadmin must hate you! The passwd(5) name field is longer than a giant static buffer. SEE ALSO
git-commit-tree(1) git-tag(1) git-config(1) GIT
Part of the git(1) suite Git 1.7.10.4 11/24/2012 GIT-VAR(1)

Check Out this Related Man Page

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 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. 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) GIT
Part of the git(1) suite Git 1.8.3.1 06/10/2014 GIT-REPLACE(1)
Man Page