git-sh-setup(1) [suse man page]

GIT-SH-SETUP(1) 						    Git Manual							   GIT-SH-SETUP(1)

NAME

       git-sh-setup - Common git shell script setup code

SYNOPSIS

       . "$(git --exec-path)/git-sh-setup"

DESCRIPTION

       This is not a command the end user would want to run. Ever. This documentation is meant for people who are studying the Porcelain-ish
       scripts and/or are writing new ones.

       The git sh-setup scriptlet is designed to be sourced (using .) by other shell scripts to set up some variables pointing at the normal git
       directories and a few helper shell functions.

       Before sourcing it, your script should set up a few variables; USAGE (and LONG_USAGE, if any) is used to define message given by usage()
       shell function. SUBDIRECTORY_OK can be set if the script can run from a subdirectory of the working tree (some commands do not).

       The scriptlet sets GIT_DIR and GIT_OBJECT_DIRECTORY shell variables, but does not export them to the environment.

FUNCTIONS

       die
	   exit after emitting the supplied error message to the standard error stream.

       usage
	   die with the usage message.

       set_reflog_action
	   set the message that will be recorded to describe the end-user action in the reflog, when the script updates a ref.

       git_editor
	   runs an editor of user's choice (GIT_EDITOR, core.editor, VISUAL or EDITOR) on a given file, but error out if no editor is specified
	   and the terminal is dumb.

       is_bare_repository
	   outputs true or false to the standard output stream to indicate if the repository is a bare repository (i.e. without an associated
	   working tree).

       cd_to_toplevel
	   runs chdir to the toplevel of the working tree.

       require_work_tree
	   checks if the repository is a bare repository, and dies if so. Used by scripts that require working tree (e.g.  checkout).

       get_author_ident_from_commit
	   outputs code for use with eval to set the GIT_AUTHOR_NAME, GIT_AUTHOR_EMAIL and GIT_AUTHOR_DATE variables for a given commit.

AUTHOR

       Written by Linus Torvalds <torvalds@osdl.org[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. torvalds@osdl.org
	   mailto:torvalds@osdl.org

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

Git 1.7.1							    07/05/2010							   GIT-SH-SETUP(1)

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

AUTHOR

       Written by Eric Biederman <ebiederm@xmission.com[1]>

DOCUMENTATION

       Documentation by Eric Biederman and the git-list <git@vger.kernel.org[2]>.

GIT

       Part of the git(1) suite

NOTES

	1. ebiederm@xmission.com
	   mailto:ebiederm@xmission.com

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

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

Linux and UNIX Man Pages

git-sh-setup(1) [suse man page]

Check Out this Related Man Page