MAJOR=4 MINOR=52 DEVNAME=tty52 MAJOR=4 MINOR=48 DEVNAME=tty48 +ˆl–Ðz¾”ËmJeAàq¶ÔÅ£Á ƒ Í7_‡I|¥ŠèªÁÀ5git-var(1) ========== NAME ---- git-var - Show a Git logical variable SYNOPSIS -------- [verse] 'git var' ( -l | ) 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 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 Files\Vim\gvim.exe" --nofork`. The order of preference is the `$GIT_EDITOR` environment variable, then `core.editor` configuration, then `$VISUAL`, then `$EDITOR`, and then the default chosen at compile time, which is usually 'vi'. ifdef::git-default-editor[] The build you are using chose '{git-default-editor}' as the default. endif::git-default-editor[] 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 the default chosen at compile time (usually 'less'). ifdef::git-default-pager[] The build you are using chose '{git-default-pager}' as the default. endif::git-default-pager[] SEE ALSO -------- linkgit:git-commit-tree[1] linkgit:git-tag[1] linkgit:git-config[1] GIT --- Part of the linkgit:git[1] suite ˆÃ ƒh¹ÁÀMAJOR=4 MINOR=29 DEVNAME=tty29 $ ˆ¿Â „ Bp_¾a–ß=¿J µ2ÛR‚œP"¸n6Ú˜´oÁ7¶ git-send-email(1) ================= NAME ---- git-send-email - Send a collection of patches as emails SYNOPSIS -------- [verse] 'git send-email' [options] ... DESCRIPTION ----------- Takes the patches given on the command line and emails them out. Patches can be specified as files, directories (which will send all files in the directory), or directly as a revision list. In the last case, any format accepted by linkgit:git-format-patch[1] can be passed to git send-email. The header of the email is configurable by command line options. If not specified on the command line, the user will be prompted with a ReadLine enabled interface to provide the necessary information. There are two formats accepted for patch files: 1. mbox format files + This is what linkgit:git-format-patch[1] generates. Most headers and MIME formatting are ignored. 2. The original format used by Greg Kroah-Hartman's 'send_lots_of_email.pl' script + This format expects the first line of the file to contain the "Cc:" value and the "Subject:" of the message as the second line. OPTIONS ------- Composing ~~~~~~~~~ --annotate:: Review and edit each patch you're about to send. Default is the value of 'sendemail.annotate'. See the CONFIGURATION section for 'sendemail.multiedit'. --bcc=
:: Specify a "Bcc:" value for each email. Default is the value of 'sendemail.bcc'. + The --bcc option must be repeated for each user you want on the bcc list. --cc=
:: Specify a starting "Cc:" value for each email. Default is the value of 'sendemail.cc'. + The --cc option must be repeated for each user you want on the cc list. --compose:: Invoke a text editor (see GIT_EDITOR in linkgit:git-var[1]) to edit an introductory message for the patch series. + When '--compose' is used, git send-email will use the From, Subject, and In-Reply-To headers specified in the message. If the body of the message (what you type after the headers and a blank line) only con