Ergebnis für URL: http://kernel.org/pub/software/scm/git/docs/git(1) Manual Page
NAME
git - the stupid content tracker
SYNOPSIS
git [-v | --version] [-h | --help] [-C ] [-c =]
[--exec-path[=]] [--html-path] [--man-path] [--info-path]
[-p|--paginate|-P|--no-pager] [--no-replace-objects] [--bare]
[--git-dir=] [--work-tree=] [--namespace=]
[--config-env==] []
DESCRIPTION
Git is a fast, scalable, distributed revision control system with an unusually
rich command set that provides both high-level operations and full access to
internals.
See [1]gittutorial(7) to get started, then see [2]giteveryday(7) for a useful
minimum set of commands. The [3]Git User's Manual has a more in-depth
introduction.
After you mastered the basic concepts, you can come back to this page to learn
what commands Git offers. You can learn more about individual Git commands with
"git help command". [4]gitcli(7) manual page gives you an overview of the
command-line command syntax.
A formatted and hyperlinked copy of the latest Git documentation can be viewed at
[5]https://git.github.io/htmldocs/git.html or [6]https://git-scm.com/docs.
OPTIONS
-v
--version
Prints the Git suite version that the git program came from.
This option is internally converted to git version ... and accepts the
same options as the [7]git-version(1) command. If --help is also given, it
takes precedence over --version.
-h
--help
Prints the synopsis and a list of the most commonly used commands. If the
option --all or -a is given then all available commands are printed. If a
Git command is named this option will bring up the manual page for that
command.
Other options are available to control how the manual page is displayed.
See [8]git-help(1) for more information, because git --help ... is
converted internally into git help ....
-C
Run as if git was started in instead of the current working
directory. When multiple -C options are given, each subsequent
non-absolute -C is interpreted relative to the preceding -C .
If is present but empty, e.g. -C "", then the current working
directory is left unchanged.
This option affects options that expect path name like --git-dir and
--work-tree in that their interpretations of the path names would be made
relative to the working directory caused by the -C option. For example the
following invocations are equivalent:
git --git-dir=a.git --work-tree=b -C c status
git --git-dir=c/a.git --work-tree=c/b status
-c =
Pass a configuration parameter to the command. The value given will
override values from configuration files. The is expected in the
same format as listed by git config (subkeys separated by dots).
Note that omitting the = in git -c foo.bar ... is allowed and sets foo.bar
to the boolean true value (just like [foo]bar would in a config file).
Including the equals but with an empty value (like git -c foo.bar= ...)
sets foo.bar to the empty string which git config --type=bool will convert
to false.
--config-env==
Like -c =, give configuration variable a value, where
is the name of an environment variable from which to retrieve the
value. Unlike -c there is no shortcut for directly setting the value to an
empty string, instead the environment variable itself must be set to the
empty string. It is an error if the does not exist in the
environment. may not contain an equals sign to avoid ambiguity
with containing one.
This is useful for cases where you want to pass transitory configuration
options to git, but are doing so on operating systems where other
processes might be able to read your command line (e.g.
/proc/self/cmdline), but not your environment (e.g. /proc/self/environ).
That behavior is the default on Linux, but may not be on your system.
Note that this might add security for variables such as http.extraHeader
where the sensitive information is part of the value, but not e.g.
url..insteadOf where the sensitive information can be part of the
key.
--exec-path[=]
Path to wherever your core Git programs are installed. This can also be
controlled by setting the GIT_EXEC_PATH environment variable. If no path
is given, git will print the current setting and then exit.
--html-path
Print the path, without trailing slash, where Git's HTML documentation is
installed and exit.
--man-path
Print the manpath (see man(1)) for the man pages for this version of Git
and exit.
--info-path
Print the path where the Info files documenting this version of Git are
installed and exit.
-p
--paginate
Pipe all output into less (or if set, $PAGER) if standard output is a
terminal. This overrides the pager. configuration options (see the
"Configuration Mechanism" section below).
-P
--no-pager
Do not pipe Git output into a pager.
--git-dir=
Set the path to the repository (".git" directory). This can also be
controlled by setting the GIT_DIR environment variable. It can be an
absolute path or relative path to current working directory.
Specifying the location of the ".git" directory using this option (or
GIT_DIR environment variable) turns off the repository discovery that
tries to find a directory with ".git" subdirectory (which is how the
repository and the top-level of the working tree are discovered), and
tells Git that you are at the top level of the working tree. If you are
not at the top-level directory of the working tree, you should tell Git
where the top-level of the working tree is, with the --work-tree=
option (or GIT_WORK_TREE environment variable)
If you just want to run git as if it was started in then use git -C
.
--work-tree=
Set the path to the working tree. It can be an absolute path or a path
relative to the current working directory. This can also be controlled by
setting the GIT_WORK_TREE environment variable and the core.worktree
configuration variable (see core.worktree in [9]git-config(1) for a more
detailed discussion).
--namespace=
Set the Git namespace. See [10]gitnamespaces(7) for more details.
Equivalent to setting the GIT_NAMESPACE environment variable.
--bare
Treat the repository as a bare repository. If GIT_DIR environment is not
set, it is set to the current working directory.
--no-replace-objects
Do not use replacement refs to replace Git objects. This is equivalent to
exporting the GIT_NO_REPLACE_OBJECTS environment variable with any value.
See [11]git-replace(1) for more information.
--no-lazy-fetch
Do not fetch missing objects from the promisor remote on demand. Useful
together with git cat-file -e to see if the object is locally
available. This is equivalent to setting the GIT_NO_LAZY_FETCH environment
variable to 1.
--literal-pathspecs
Treat pathspecs literally (i.e. no globbing, no pathspec magic). This is
equivalent to setting the GIT_LITERAL_PATHSPECS environment variable to 1.
--glob-pathspecs
Add "glob" magic to all pathspec. This is equivalent to setting the
GIT_GLOB_PATHSPECS environment variable to 1. Disabling globbing on
individual pathspecs can be done using pathspec magic ":(literal)"
--noglob-pathspecs
Add "literal" magic to all pathspec. This is equivalent to setting the
GIT_NOGLOB_PATHSPECS environment variable to 1. Enabling globbing on
individual pathspecs can be done using pathspec magic ":(glob)"
--icase-pathspecs
Add "icase" magic to all pathspec. This is equivalent to setting the
GIT_ICASE_PATHSPECS environment variable to 1.
--no-optional-locks
Do not perform optional operations that require locks. This is equivalent
to setting the GIT_OPTIONAL_LOCKS to 0.
--list-cmds=[,...]
List commands by group. This is an internal/experimental option and may
change or be removed in the future. Supported groups are: builtins,
parseopt (builtin commands that use parse-options), main (all commands in
libexec directory), others (all other commands in $PATH that have git-
prefix), list- (see categories in command-list.txt), nohelpers
(exclude helper commands), alias and config (retrieve command list from
config variable completion.commands)
--attr-source=
Read gitattributes from instead of the worktree. See
[12]gitattributes(5). This is equivalent to setting the GIT_ATTR_SOURCE
environment variable.
GIT COMMANDS
We divide Git into high level ("porcelain") commands and low level ("plumbing")
commands.
High-level commands (porcelain)
We separate the porcelain commands into the main commands and some ancillary user
utilities.
Main porcelain commands
[13]git-add(1)
Add file contents to the index.
[14]git-am(1)
Apply a series of patches from a mailbox.
[15]git-archive(1)
Create an archive of files from a named tree.
[16]git-bisect(1)
Use binary search to find the commit that introduced a bug.
[17]git-branch(1)
List, create, or delete branches.
[18]git-bundle(1)
Move objects and refs by archive.
[19]git-checkout(1)
Switch branches or restore working tree files.
[20]git-cherry-pick(1)
Apply the changes introduced by some existing commits.
[21]git-citool(1)
Graphical alternative to git-commit.
[22]git-clean(1)
Remove untracked files from the working tree.
[23]git-clone(1)
Clone a repository into a new directory.
[24]git-commit(1)
Record changes to the repository.
[25]git-describe(1)
Give an object a human readable name based on an available ref.
[26]git-diff(1)
Show changes between commits, commit and working tree, etc.
[27]git-fetch(1)
Download objects and refs from another repository.
[28]git-format-patch(1)
Prepare patches for e-mail submission.
[29]git-gc(1)
Cleanup unnecessary files and optimize the local repository.
[30]git-grep(1)
Print lines matching a pattern.
[31]git-gui(1)
A portable graphical interface to Git.
[32]git-init(1)
Create an empty Git repository or reinitialize an existing one.
[33]git-log(1)
Show commit logs.
[34]git-maintenance(1)
Run tasks to optimize Git repository data.
[35]git-merge(1)
Join two or more development histories together.
[36]git-mv(1)
Move or rename a file, a directory, or a symlink.
[37]git-notes(1)
Add or inspect object notes.
[38]git-pull(1)
Fetch from and integrate with another repository or a local branch.
[39]git-push(1)
Update remote refs along with associated objects.
[40]git-range-diff(1)
Compare two commit ranges (e.g. two versions of a branch).
[41]git-rebase(1)
Reapply commits on top of another base tip.
[42]git-reset(1)
Reset current HEAD to the specified state.
[43]git-restore(1)
Restore working tree files.
[44]git-revert(1)
Revert some existing commits.
[45]git-rm(1)
Remove files from the working tree and from the index.
[46]git-shortlog(1)
Summarize git log output.
[47]git-show(1)
Show various types of objects.
[48]git-sparse-checkout(1)
Reduce your working tree to a subset of tracked files.
[49]git-stash(1)
Stash the changes in a dirty working directory away.
[50]git-status(1)
Show the working tree status.
[51]git-submodule(1)
Initialize, update or inspect submodules.
[52]git-switch(1)
Switch branches.
[53]git-tag(1)
Create, list, delete or verify a tag object signed with GPG.
[54]git-worktree(1)
Manage multiple working trees.
[55]gitk(1)
The Git repository browser.
[56]scalar(1)
A tool for managing large Git repositories.
Ancillary Commands
Manipulators:
[57]git-config(1)
Get and set repository or global options.
[58]git-fast-export(1)
Git data exporter.
[59]git-fast-import(1)
Backend for fast Git data importers.
[60]git-filter-branch(1)
Rewrite branches.
[61]git-mergetool(1)
Run merge conflict resolution tools to resolve merge conflicts.
[62]git-pack-refs(1)
Pack heads and tags for efficient repository access.
[63]git-prune(1)
Prune all unreachable objects from the object database.
[64]git-reflog(1)
Manage reflog information.
[65]git-remote(1)
Manage set of tracked repositories.
[66]git-repack(1)
Pack unpacked objects in a repository.
[67]git-replace(1)
Create, list, delete refs to replace objects.
Interrogators:
[68]git-annotate(1)
Annotate file lines with commit information.
[69]git-blame(1)
Show what revision and author last modified each line of a file.
[70]git-bugreport(1)
Collect information for user to file a bug report.
[71]git-count-objects(1)
Count unpacked number of objects and their disk consumption.
[72]git-diagnose(1)
Generate a zip archive of diagnostic information.
[73]git-difftool(1)
Show changes using common diff tools.
[74]git-fsck(1)
Verifies the connectivity and validity of the objects in the database.
[75]git-help(1)
Display help information about Git.
[76]git-instaweb(1)
Instantly browse your working repository in gitweb.
[77]git-merge-tree(1)
Perform merge without touching index or working tree.
[78]git-rerere(1)
Reuse recorded resolution of conflicted merges.
[79]git-show-branch(1)
Show branches and their commits.
[80]git-verify-commit(1)
Check the GPG signature of commits.
[81]git-verify-tag(1)
Check the GPG signature of tags.
[82]git-version(1)
Display version information about Git.
[83]git-whatchanged(1)
Show logs with differences each commit introduces.
[84]gitweb(1)
Git web interface (web frontend to Git repositories).
Interacting with Others
These commands are to interact with foreign SCM and with other people via patch
over e-mail.
[85]git-archimport(1)
Import a GNU Arch repository into Git.
[86]git-cvsexportcommit(1)
Export a single commit to a CVS checkout.
[87]git-cvsimport(1)
Salvage your data out of another SCM people love to hate.
[88]git-cvsserver(1)
A CVS server emulator for Git.
[89]git-imap-send(1)
Send a collection of patches from stdin to an IMAP folder.
[90]git-p4(1)
Import from and submit to Perforce repositories.
[91]git-quiltimport(1)
Applies a quilt patchset onto the current branch.
[92]git-request-pull(1)
Generates a summary of pending changes.
[93]git-send-email(1)
Send a collection of patches as emails.
[94]git-svn(1)
Bidirectional operation between a Subversion repository and Git.
Reset, restore and revert
There are three commands with similar names: git reset, git restore and git
revert.
* [95]git-revert(1) is about making a new commit that reverts the changes made
by other commits.
* [96]git-restore(1) is about restoring files in the working tree from either
the index or another commit. This command does not update your branch. The
command can also be used to restore files in the index from another commit.
* [97]git-reset(1) is about updating your branch, moving the tip in order to
add or remove commits from the branch. This operation changes the commit
history.
git reset can also be used to restore the index, overlapping with git
restore.
Low-level commands (plumbing)
Although Git includes its own porcelain layer, its low-level commands are
sufficient to support development of alternative porcelains. Developers of such
porcelains might start by reading about [98]git-update-index(1) and
[99]git-read-tree(1).
The interface (input, output, set of options and the semantics) to these
low-level commands are meant to be a lot more stable than Porcelain level
commands, because these commands are primarily for scripted use. The interface to
Porcelain commands on the other hand are subject to change in order to improve
the end user experience.
The following description divides the low-level commands into commands that
manipulate objects (in the repository, index, and working tree), commands that
interrogate and compare objects, and commands that move objects and references
between repositories.
Manipulation commands
[100]git-apply(1)
Apply a patch to files and/or to the index.
[101]git-checkout-index(1)
Copy files from the index to the working tree.
[102]git-commit-graph(1)
Write and verify Git commit-graph files.
[103]git-commit-tree(1)
Create a new commit object.
[104]git-hash-object(1)
Compute object ID and optionally create an object from a file.
[105]git-index-pack(1)
Build pack index file for an existing packed archive.
[106]git-merge-file(1)
Run a three-way file merge.
[107]git-merge-index(1)
Run a merge for files needing merging.
[108]git-mktag(1)
Creates a tag object with extra validation.
[109]git-mktree(1)
Build a tree-object from ls-tree formatted text.
[110]git-multi-pack-index(1)
Write and verify multi-pack-indexes.
[111]git-pack-objects(1)
Create a packed archive of objects.
[112]git-prune-packed(1)
Remove extra objects that are already in pack files.
[113]git-read-tree(1)
Reads tree information into the index.
[114]git-replay(1)
EXPERIMENTAL: Replay commits on a new base, works with bare repos too.
[115]git-symbolic-ref(1)
Read, modify and delete symbolic refs.
[116]git-unpack-objects(1)
Unpack objects from a packed archive.
[117]git-update-index(1)
Register file contents in the working tree to the index.
[118]git-update-ref(1)
Update the object name stored in a ref safely.
[119]git-write-tree(1)
Create a tree object from the current index.
Interrogation commands
[120]git-cat-file(1)
Provide contents or details of repository objects.
[121]git-cherry(1)
Find commits yet to be applied to upstream.
[122]git-diff-files(1)
Compares files in the working tree and the index.
[123]git-diff-index(1)
Compare a tree to the working tree or index.
[124]git-diff-tree(1)
Compares the content and mode of blobs found via two tree objects.
[125]git-for-each-ref(1)
Output information on each ref.
[126]git-for-each-repo(1)
Run a Git command on a list of repositories.
[127]git-get-tar-commit-id(1)
Extract commit ID from an archive created using git-archive.
[128]git-ls-files(1)
Show information about files in the index and the working tree.
[129]git-ls-remote(1)
List references in a remote repository.
[130]git-ls-tree(1)
List the contents of a tree object.
[131]git-merge-base(1)
Find as good common ancestors as possible for a merge.
[132]git-name-rev(1)
Find symbolic names for given revs.
[133]git-pack-redundant(1)
Find redundant pack files.
[134]git-rev-list(1)
Lists commit objects in reverse chronological order.
[135]git-rev-parse(1)
Pick out and massage parameters.
[136]git-show-index(1)
Show packed archive index.
[137]git-show-ref(1)
List references in a local repository.
[138]git-unpack-file(1)
Creates a temporary file with a blob's contents.
[139]git-var(1)
Show a Git logical variable.
[140]git-verify-pack(1)
Validate packed Git archive files.
In general, the interrogate commands do not touch the files in the working tree.
Syncing repositories
[141]git-daemon(1)
A really simple server for Git repositories.
[142]git-fetch-pack(1)
Receive missing objects from another repository.
[143]git-http-backend(1)
Server side implementation of Git over HTTP.
[144]git-send-pack(1)
Push objects over Git protocol to another repository.
[145]git-update-server-info(1)
Update auxiliary info file to help dumb servers.
The following are helper commands used by the above; end users typically do not
use them directly.
[146]git-http-fetch(1)
Download from a remote Git repository via HTTP.
[147]git-http-push(1)
Push objects over HTTP/DAV to another repository.
[148]git-receive-pack(1)
Receive what is pushed into the repository.
[149]git-shell(1)
Restricted login shell for Git-only SSH access.
[150]git-upload-archive(1)
Send archive back to git-archive.
[151]git-upload-pack(1)
Send objects packed back to git-fetch-pack.
Internal helper commands
These are internal helper commands used by other commands; end users typically do
not use them directly.
[152]git-check-attr(1)
Display gitattributes information.
[153]git-check-ignore(1)
Debug gitignore / exclude files.
[154]git-check-mailmap(1)
Show canonical names and email addresses of contacts.
[155]git-check-ref-format(1)
Ensures that a reference name is well formed.
[156]git-column(1)
Display data in columns.
[157]git-credential(1)
Retrieve and store user credentials.
[158]git-credential-cache(1)
Helper to temporarily store passwords in memory.
[159]git-credential-store(1)
Helper to store credentials on disk.
[160]git-fmt-merge-msg(1)
Produce a merge commit message.
[161]git-hook(1)
Run git hooks.
[162]git-interpret-trailers(1)
Add or parse structured information in commit messages.
[163]git-mailinfo(1)
Extracts patch and authorship from a single e-mail message.
[164]git-mailsplit(1)
Simple UNIX mbox splitter program.
[165]git-merge-one-file(1)
The standard helper program to use with git-merge-index.
[166]git-patch-id(1)
Compute unique ID for a patch.
[167]git-sh-i18n(1)
Git's i18n setup code for shell scripts.
[168]git-sh-setup(1)
Common Git shell script setup code.
[169]git-stripspace(1)
Remove unnecessary whitespace.
Guides
The following documentation pages are guides about Git concepts.
[170]gitcore-tutorial(7)
A Git core tutorial for developers.
[171]gitcredentials(7)
Providing usernames and passwords to Git.
[172]gitcvs-migration(7)
Git for CVS users.
[173]gitdiffcore(7)
Tweaking diff output.
[174]giteveryday(7)
A useful minimum set of commands for Everyday Git.
[175]gitfaq(7)
Frequently asked questions about using Git.
[176]gitglossary(7)
A Git Glossary.
[177]gitnamespaces(7)
Git namespaces.
[178]gitremote-helpers(7)
Helper programs to interact with remote repositories.
[179]gitsubmodules(7)
Mounting one repository inside another.
[180]gittutorial(7)
A tutorial introduction to Git.
[181]gittutorial-2(7)
A tutorial introduction to Git: part two.
[182]gitworkflows(7)
An overview of recommended workflows with Git.
Repository, command and file interfaces
This documentation discusses repository and command interfaces which users are
expected to interact with directly. See --user-formats in [183]git-help(1) for
more details on the criteria.
[184]gitattributes(5)
Defining attributes per path.
[185]gitcli(7)
Git command-line interface and conventions.
[186]githooks(5)
Hooks used by Git.
[187]gitignore(5)
Specifies intentionally untracked files to ignore.
[188]gitmailmap(5)
Map author/committer names and/or E-Mail addresses.
[189]gitmodules(5)
Defining submodule properties.
[190]gitrepository-layout(5)
Git Repository Layout.
[191]gitrevisions(7)
Specifying revisions and ranges for Git.
File formats, protocols and other developer interfaces
This documentation discusses file formats, over-the-wire protocols and other git
developer interfaces. See --developer-interfaces in [192]git-help(1).
[193]gitformat-bundle(5)
The bundle file format.
[194]gitformat-chunk(5)
Chunk-based file formats.
[195]gitformat-commit-graph(5)
Git commit-graph format.
[196]gitformat-index(5)
Git index format.
[197]gitformat-pack(5)
Git pack format.
[198]gitformat-signature(5)
Git cryptographic signature formats.
[199]gitprotocol-capabilities(5)
Protocol v0 and v1 capabilities.
[200]gitprotocol-common(5)
Things common to various protocols.
[201]gitprotocol-http(5)
Git HTTP-based protocols.
[202]gitprotocol-pack(5)
How packs are transferred over-the-wire.
[203]gitprotocol-v2(5)
Git Wire Protocol, Version 2.
Configuration Mechanism
Git uses a simple text format to store customizations that are per repository and
are per user. Such a configuration file may look like this:
#
# A '#' or ';' character indicates a comment.
#
; core variables
[core]
; Don't trust file modes
filemode = false
; user identity
[user]
name = "Junio C Hamano"
email = "gitster@pobox.com"
Various commands read from the configuration file and adjust their operation
accordingly. See [204]git-config(1) for a list and more details about the
configuration mechanism.
Identifier Terminology
Indicates the object name for any type of object.
Indicates a blob object name.
Indicates a tree object name.
Indicates a commit object name.
Indicates a tree, commit or tag object name. A command that takes a
argument ultimately wants to operate on a object but
automatically dereferences and objects that point at a
.
Indicates a commit or tag object name. A command that takes a
argument ultimately wants to operate on a object but
automatically dereferences objects that point at a .
Indicates that an object type is required. Currently one of: blob, tree,
commit, or tag.
Indicates a filename - almost always relative to the root of the tree
structure GIT_INDEX_FILE describes.
Symbolic Identifiers
Any Git command accepting any can also use the following symbolic
notation:
HEAD
indicates the head of the current branch.
a valid tag name (i.e. a refs/tags/ reference).
a valid head name (i.e. a refs/heads/ reference).
For a more complete list of ways to spell object names, see "SPECIFYING
REVISIONS" section in [205]gitrevisions(7).
File/Directory Structure
Please see the [206]gitrepository-layout(5) document.
Read [207]githooks(5) for more details about each hook.
Higher level SCMs may provide and manage additional information in the $GIT_DIR.
Terminology
Please see [208]gitglossary(7).
Environment Variables
Various Git commands pay attention to environment variables and change their
behavior. The environment variables marked as "Boolean" take their values the
same way as Boolean valued configuration variables, e.g. "true", "yes", "on" and
positive numbers are taken as "yes".
Here are the variables:
The Git Repository
These environment variables apply to all core Git commands. Nb: it is worth
noting that they may be used/overridden by SCMS sitting above Git so take care if
using a foreign front-end.
GIT_INDEX_FILE
This environment variable specifies an alternate index file. If not
specified, the default of $GIT_DIR/index is used.
GIT_INDEX_VERSION
This environment variable specifies what index version is used when
writing the index file out. It won't affect existing index files. By
default index file version 2 or 3 is used. See [209]git-update-index(1)
for more information.
GIT_OBJECT_DIRECTORY
If the object storage directory is specified via this environment variable
then the sha1 directories are created underneath - otherwise the default
$GIT_DIR/objects directory is used.
GIT_ALTERNATE_OBJECT_DIRECTORIES
Due to the immutable nature of Git objects, old objects can be archived
into shared, read-only directories. This variable specifies a ":"
separated (on Windows ";" separated) list of Git object directories which
can be used to search for Git objects. New objects will not be written to
these directories.
Entries that begin with " (double-quote) will be interpreted as C-style
quoted paths, removing leading and trailing double-quotes and respecting
backslash escapes. E.g., the value "path-with-\"-and-:-in-it":vanilla-path
has two paths: path-with-"-and-:-in-it and vanilla-path.
GIT_DIR
If the GIT_DIR environment variable is set then it specifies a path to use
instead of the default .git for the base of the repository. The --git-dir
command-line option also sets this value.
GIT_WORK_TREE
Set the path to the root of the working tree. This can also be controlled
by the --work-tree command-line option and the core.worktree configuration
variable.
GIT_NAMESPACE
Set the Git namespace; see [210]gitnamespaces(7) for details. The
--namespace command-line option also sets this value.
GIT_CEILING_DIRECTORIES
This should be a colon-separated list of absolute paths. If set, it is a
list of directories that Git should not chdir up into while looking for a
repository directory (useful for excluding slow-loading network
directories). It will not exclude the current working directory or a
GIT_DIR set on the command line or in the environment. Normally, Git has
to read the entries in this list and resolve any symlink that might be
present in order to compare them with the current directory. However, if
even this access is slow, you can add an empty entry to the list to tell
Git that the subsequent entries are not symlinks and needn't be resolved;
e.g., GIT_CEILING_DIRECTORIES=/maybe/symlink::/very/slow/non/symlink.
GIT_DISCOVERY_ACROSS_FILESYSTEM
When run in a directory that does not have ".git" repository directory,
Git tries to find such a directory in the parent directories to find the
top of the working tree, but by default it does not cross filesystem
boundaries. This Boolean environment variable can be set to true to tell
Git not to stop at filesystem boundaries. Like GIT_CEILING_DIRECTORIES,
this will not affect an explicit repository directory set via GIT_DIR or
on the command line.
GIT_COMMON_DIR
If this variable is set to a path, non-worktree files that are normally in
$GIT_DIR will be taken from this path instead. Worktree-specific files
such as HEAD or index are taken from $GIT_DIR. See
[211]gitrepository-layout(5) and [212]git-worktree(1) for details. This
variable has lower precedence than other path variables such as
GIT_INDEX_FILE, GIT_OBJECT_DIRECTORY...
GIT_DEFAULT_HASH
If this variable is set, the default hash algorithm for new repositories
will be set to this value. This value is ignored when cloning and the
setting of the remote repository is always used. The default is "sha1".
See --object-format in [213]git-init(1).
GIT_DEFAULT_REF_FORMAT
If this variable is set, the default reference backend format for new
repositories will be set to this value. The default is "files". See
--ref-format in [214]git-init(1).
Git Commits
GIT_AUTHOR_NAME
The human-readable name used in the author identity when creating commit
or tag objects, or when writing reflogs. Overrides the user.name and
author.name configuration settings.
GIT_AUTHOR_EMAIL
The email address used in the author identity when creating commit or tag
objects, or when writing reflogs. Overrides the user.email and
author.email configuration settings.
GIT_AUTHOR_DATE
The date used for the author identity when creating commit or tag objects,
or when writing reflogs. See [215]git-commit(1) for valid formats.
GIT_COMMITTER_NAME
The human-readable name used in the committer identity when creating
commit or tag objects, or when writing reflogs. Overrides the user.name
and committer.name configuration settings.
GIT_COMMITTER_EMAIL
The email address used in the author identity when creating commit or tag
objects, or when writing reflogs. Overrides the user.email and
committer.email configuration settings.
GIT_COMMITTER_DATE
The date used for the committer identity when creating commit or tag
objects, or when writing reflogs. See [216]git-commit(1) for valid
formats.
EMAIL
The email address used in the author and committer identities if no other
relevant environment variable or configuration setting has been set.
Git Diffs
GIT_DIFF_OPTS
Only valid setting is "--unified=??" or "-u??" to set the number of
context lines shown when a unified diff is created. This takes precedence
over any "-U" or "--unified" option value passed on the Git diff command
line.
GIT_EXTERNAL_DIFF
When the environment variable GIT_EXTERNAL_DIFF is set, the program named
by it is called to generate diffs, and Git does not use its builtin diff
machinery. For a path that is added, removed, or modified,
GIT_EXTERNAL_DIFF is called with 7 parameters:
path old-file old-hex old-mode new-file new-hex new-mode
where:
-file
are files GIT_EXTERNAL_DIFF can use to read the contents of ,
-hex
are the 40-hexdigit SHA-1 hashes,
-mode
are the octal representation of the file modes.
The file parameters can point at the user's working file (e.g. new-file in
"git-diff-files"), /dev/null (e.g. old-file when a new file is added), or
a temporary file (e.g. old-file in the index). GIT_EXTERNAL_DIFF should
not worry about unlinking the temporary file -- it is removed when
GIT_EXTERNAL_DIFF exits.
For a path that is unmerged, GIT_EXTERNAL_DIFF is called with 1 parameter,
.
For each path GIT_EXTERNAL_DIFF is called, two environment variables,
GIT_DIFF_PATH_COUNTER and GIT_DIFF_PATH_TOTAL are set.
GIT_DIFF_PATH_COUNTER
A 1-based counter incremented by one for every path.
GIT_DIFF_PATH_TOTAL
The total number of paths.
other
GIT_MERGE_VERBOSITY
A number controlling the amount of output shown by the recursive merge
strategy. Overrides merge.verbosity. See [217]git-merge(1)
GIT_PAGER
This environment variable overrides $PAGER. If it is set to an empty
string or to the value "cat", Git will not launch a pager. See also the
core.pager option in [218]git-config(1).
GIT_PROGRESS_DELAY
A number controlling how many seconds to delay before showing optional
progress indicators. Defaults to 2.
GIT_EDITOR
This environment variable overrides $EDITOR and $VISUAL. It is used by
several Git commands when, on interactive mode, an editor is to be
launched. See also [219]git-var(1) and the core.editor option in
[220]git-config(1).
GIT_SEQUENCE_EDITOR
This environment variable overrides the configured Git editor when editing
the todo list of an interactive rebase. See also [221]git-rebase(1) and
the sequence.editor option in [222]git-config(1).
GIT_SSH
GIT_SSH_COMMAND
If either of these environment variables is set then git fetch and git
push will use the specified command instead of ssh when they need to
connect to a remote system. The command-line parameters passed to the
configured command are determined by the ssh variant. See ssh.variant
option in [223]git-config(1) for details.
$GIT_SSH_COMMAND takes precedence over $GIT_SSH, and is interpreted by the
shell, which allows additional arguments to be included. $GIT_SSH on the
other hand must be just the path to a program (which can be a wrapper
shell script, if additional arguments are needed).
Usually it is easier to configure any desired options through your
personal .ssh/config file. Please consult your ssh documentation for
further details.
GIT_SSH_VARIANT
If this environment variable is set, it overrides Git's autodetection
whether GIT_SSH/GIT_SSH_COMMAND/core.sshCommand refer to OpenSSH, plink or
tortoiseplink. This variable overrides the config setting ssh.variant that
serves the same purpose.
GIT_SSL_NO_VERIFY
Setting and exporting this environment variable to any value tells Git not
to verify the SSL certificate when fetching or pushing over HTTPS.
GIT_ATTR_SOURCE
Sets the treeish that gitattributes will be read from.
GIT_ASKPASS
If this environment variable is set, then Git commands which need to
acquire passwords or passphrases (e.g. for HTTP or IMAP authentication)
will call this program with a suitable prompt as command-line argument and
read the password from its STDOUT. See also the core.askPass option in
[224]git-config(1).
GIT_TERMINAL_PROMPT
If this Boolean environment variable is set to false, git will not prompt
on the terminal (e.g., when asking for HTTP authentication).
GIT_CONFIG_GLOBAL
GIT_CONFIG_SYSTEM
Take the configuration from the given files instead from global or
system-level configuration files. If GIT_CONFIG_SYSTEM is set, the system
config file defined at build time (usually /etc/gitconfig) will not be
read. Likewise, if GIT_CONFIG_GLOBAL is set, neither $HOME/.gitconfig nor
$XDG_CONFIG_HOME/git/config will be read. Can be set to /dev/null to skip
reading configuration files of the respective level.
GIT_CONFIG_NOSYSTEM
Whether to skip reading settings from the system-wide
$(prefix)/etc/gitconfig file. This Boolean environment variable can be
used along with $HOME and $XDG_CONFIG_HOME to create a predictable
environment for a picky script, or you can set it to true to temporarily
avoid using a buggy /etc/gitconfig file while waiting for someone with
sufficient permissions to fix it.
GIT_FLUSH
If this Boolean environment variable is set to true, then commands such as
git blame (in incremental mode), git rev-list, git log, git check-attr and
git check-ignore will force a flush of the output stream after each record
have been flushed. If this variable is set to false, the output of these
commands will be done using completely buffered I/O. If this environment
variable is not set, Git will choose buffered or record-oriented flushing
based on whether stdout appears to be redirected to a file or not.
GIT_TRACE
Enables general trace messages, e.g. alias expansion, built-in command
execution and external command execution.
If this variable is set to "1", "2" or "true" (comparison is case
insensitive), trace messages will be printed to stderr.
If the variable is set to an integer value greater than 2 and lower than
10 (strictly) then Git will interpret this value as an open file
descriptor and will try to write the trace messages into this file
descriptor.
Alternatively, if the variable is set to an absolute path (starting with a
/ character), Git will interpret this as a file path and will try to
append the trace messages to it.
Unsetting the variable, or setting it to empty, "0" or "false" (case
insensitive) disables trace messages.
GIT_TRACE_FSMONITOR
Enables trace messages for the filesystem monitor extension. See GIT_TRACE
for available trace output options.
GIT_TRACE_PACK_ACCESS
Enables trace messages for all accesses to any packs. For each access, the
pack file name and an offset in the pack is recorded. This may be helpful
for troubleshooting some pack-related performance problems. See GIT_TRACE
for available trace output options.
GIT_TRACE_PACKET
Enables trace messages for all packets coming in or out of a given
program. This can help with debugging object negotiation or other protocol
issues. Tracing is turned off at a packet starting with "PACK" (but see
GIT_TRACE_PACKFILE below). See GIT_TRACE for available trace output
options.
GIT_TRACE_PACKFILE
Enables tracing of packfiles sent or received by a given program. Unlike
other trace output, this trace is verbatim: no headers, and no quoting of
binary data. You almost certainly want to direct into a file (e.g.,
GIT_TRACE_PACKFILE=/tmp/my.pack) rather than displaying it on the terminal
or mixing it with other trace output.
Note that this is currently only implemented for the client side of clones
and fetches.
GIT_TRACE_PERFORMANCE
Enables performance related trace messages, e.g. total execution time of
each Git command. See GIT_TRACE for available trace output options.
GIT_TRACE_REFS
Enables trace messages for operations on the ref database. See GIT_TRACE
for available trace output options.
GIT_TRACE_SETUP
Enables trace messages printing the .git, working tree and current working
directory after Git has completed its setup phase. See GIT_TRACE for
available trace output options.
GIT_TRACE_SHALLOW
Enables trace messages that can help debugging fetching / cloning of
shallow repositories. See GIT_TRACE for available trace output options.
GIT_TRACE_CURL
Enables a curl full trace dump of all incoming and outgoing data,
including descriptive information, of the git transport protocol. This is
similar to doing curl --trace-ascii on the command line. See GIT_TRACE for
available trace output options.
GIT_TRACE_CURL_NO_DATA
When a curl trace is enabled (see GIT_TRACE_CURL above), do not dump data
(that is, only dump info lines and headers).
GIT_TRACE2
Enables more detailed trace messages from the "trace2" library. Output
from GIT_TRACE2 is a simple text-based format for human readability.
If this variable is set to "1", "2" or "true" (comparison is case
insensitive), trace messages will be printed to stderr.
If the variable is set to an integer value greater than 2 and lower than
10 (strictly) then Git will interpret this value as an open file
descriptor and will try to write the trace messages into this file
descriptor.
Alternatively, if the variable is set to an absolute path (starting with a
/ character), Git will interpret this as a file path and will try to
append the trace messages to it. If the path already exists and is a
directory, the trace messages will be written to files (one per process)
in that directory, named according to the last component of the SID and an
optional counter (to avoid filename collisions).
In addition, if the variable is set to
af_unix:[:], Git will try to open the path
as a Unix Domain Socket. The socket type can be either stream or dgram.
Unsetting the variable, or setting it to empty, "0" or "false" (case
insensitive) disables trace messages.
See [225]Trace2 documentation for full details.
GIT_TRACE2_EVENT
This setting writes a JSON-based format that is suited for machine
interpretation. See GIT_TRACE2 for available trace output options and
[226]Trace2 documentation for full details.
GIT_TRACE2_PERF
In addition to the text-based messages available in GIT_TRACE2, this
setting writes a column-based format for understanding nesting regions.
See GIT_TRACE2 for available trace output options and [227]Trace2
documentation for full details.
GIT_TRACE_REDACT
By default, when tracing is activated, Git redacts the values of cookies,
the "Authorization:" header, the "Proxy-Authorization:" header and
packfile URIs. Set this Boolean environment variable to false to prevent
this redaction.
GIT_NO_REPLACE_OBJECTS
Setting and exporting this environment variable tells Git to ignore
replacement refs and do not replace Git objects.
GIT_LITERAL_PATHSPECS
Setting this Boolean environment variable to true will cause Git to treat
all pathspecs literally, rather than as glob patterns. For example,
running GIT_LITERAL_PATHSPECS=1 git log -- '*.c' will search for commits
that touch the path *.c, not any paths that the glob *.c matches. You
might want this if you are feeding literal paths to Git (e.g., paths
previously given to you by git ls-tree, --raw diff output, etc).
GIT_GLOB_PATHSPECS
Setting this Boolean environment variable to true will cause Git to treat
all pathspecs as glob patterns (aka "glob" magic).
GIT_NOGLOB_PATHSPECS
Setting this Boolean environment variable to true will cause Git to treat
all pathspecs as literal (aka "literal" magic).
GIT_ICASE_PATHSPECS
Setting this Boolean environment variable to true will cause Git to treat
all pathspecs as case-insensitive.
GIT_NO_LAZY_FETCH
Setting this Boolean environment variable to true tells Git not to lazily
fetch missing objects from the promisor remote on demand.
GIT_REFLOG_ACTION
When a ref is updated, reflog entries are created to keep track of the
reason why the ref was updated (which is typically the name of the
high-level command that updated the ref), in addition to the old and new
values of the ref. A scripted Porcelain command can use set_reflog_action
helper function in git-sh-setup to set its name to this variable when it
is invoked as the top level command by the end user, to be recorded in the
body of the reflog.
GIT_REF_PARANOIA
If this Boolean environment variable is set to false, ignore broken or
badly named refs when iterating over lists of refs. Normally Git will try
to include any such refs, which may cause some operations to fail. This is
usually preferable, as potentially destructive operations (e.g.,
[228]git-prune(1)) are better off aborting rather than ignoring broken
refs (and thus considering the history they point to as not worth saving).
The default value is 1 (i.e., be paranoid about detecting and aborting all
operations). You should not normally need to set this to 0, but it may be
useful when trying to salvage data from a corrupted repository.
GIT_COMMIT_GRAPH_PARANOIA
When loading a commit object from the commit-graph, Git performs an
existence check on the object in the object database. This is done to
avoid issues with stale commit-graphs that contain references to
already-deleted commits, but comes with a performance penalty.
The default is "false", which disables the aforementioned behavior.
Setting this to "true" enables the existence check so that stale commits
will never be returned from the commit-graph at the cost of performance.
GIT_ALLOW_PROTOCOL
If set to a colon-separated list of protocols, behave as if protocol.allow
is set to never, and each of the listed protocols has
protocol..allow set to always (overriding any existing
configuration). See the description of protocol.allow in
[229]git-config(1) for more details.
GIT_PROTOCOL_FROM_USER
Set this Boolean environment variable to false to prevent protocols used
by fetch/push/clone which are configured to the user state. This is useful
to restrict recursive submodule initialization from an untrusted
repository or for programs which feed potentially-untrusted URLS to git
commands. See [230]git-config(1) for more details.
GIT_PROTOCOL
For internal use only. Used in handshaking the wire protocol. Contains a
colon : separated list of keys with optional values [=].
Presence of unknown keys and values must be ignored.
Note that servers may need to be configured to allow this variable to pass
over some transports. It will be propagated automatically when accessing
local repositories (i.e., file:// or a filesystem path), as well as over
the git:// protocol. For git-over-http, it should work automatically in
most configurations, but see the discussion in [231]git-http-backend(1).
For git-over-ssh, the ssh server may need to be configured to allow
clients to pass this variable (e.g., by using AcceptEnv GIT_PROTOCOL with
OpenSSH).
This configuration is optional. If the variable is not propagated, then
clients will fall back to the original "v0" protocol (but may miss out on
some performance improvements or features). This variable currently only
affects clones and fetches; it is not yet used for pushes (but may be in
the future).
GIT_OPTIONAL_LOCKS
If this Boolean environment variable is set to false, Git will complete
any requested operation without performing any optional sub-operations
that require taking a lock. For example, this will prevent git status from
refreshing the index as a side effect. This is useful for processes
running in the background which do not want to cause lock contention with
other operations on the repository. Defaults to 1.
GIT_REDIRECT_STDIN
GIT_REDIRECT_STDOUT
GIT_REDIRECT_STDERR
Windows-only: allow redirecting the standard input/output/error handles to
paths specified by the environment variables. This is particularly useful
in multi-threaded applications where the canonical way to pass standard
handles via CreateProcess() is not an option because it would require the
handles to be marked inheritable (and consequently every spawned process
would inherit them, possibly blocking regular Git operations). The primary
intended use case is to use named pipes for communication (e.g.
\\.\pipe\my-git-stdin-123).
Two special values are supported: off will simply close the corresponding
standard handle, and if GIT_REDIRECT_STDERR is 2>&1, standard error will
be redirected to the same handle as standard output.
GIT_PRINT_SHA1_ELLIPSIS (deprecated)
If set to yes, print an ellipsis following an (abbreviated) SHA-1 value.
This affects indications of detached HEADs ([232]git-checkout(1)) and the
raw diff output ([233]git-diff(1)). Printing an ellipsis in the cases
mentioned is no longer considered adequate and support for it is likely to
be removed in the foreseeable future (along with the variable).
Discussion
More detail on the following is available from the [234]Git concepts chapter of
the user-manual and [235]gitcore-tutorial(7).
A Git project normally consists of a working directory with a ".git" subdirectory
at the top level. The .git directory contains, among other things, a compressed
object database representing the complete history of the project, an "index" file
which links that history to the current contents of the working tree, and named
pointers into that history such as tags and branch heads.
The object database contains objects of three main types: blobs, which hold file
data; trees, which point to blobs and other trees to build up directory
hierarchies; and commits, which each reference a single tree and some number of
parent commits.
The commit, equivalent to what other systems call a "changeset" or "version",
represents a step in the project's history, and each parent represents an
immediately preceding step. Commits with more than one parent represent merges of
independent lines of development.
All objects are named by the SHA-1 hash of their contents, normally written as a
string of 40 hex digits. Such names are globally unique. The entire history
leading up to a commit can be vouched for by signing just that commit. A fourth
object type, the tag, is provided for this purpose.
When first created, objects are stored in individual files, but for efficiency
may later be compressed together into "pack files".
Named pointers called refs mark interesting points in history. A ref may contain
the SHA-1 name of an object or the name of another ref (the latter is called a
"symbolic ref"). Refs with names beginning refs/head/ contain the SHA-1 name of
the most recent commit (or "head") of a branch under development. SHA-1 names of
tags of interest are stored under refs/tags/. A symbolic ref named HEAD contains
the name of the currently checked-out branch.
The index file is initialized with a list of all paths and, for each path, a blob
object and a set of attributes. The blob object represents the contents of the
file as of the head of the current branch. The attributes (last modified time,
size, etc.) are taken from the corresponding file in the working tree. Subsequent
changes to the working tree can be found by comparing these attributes. The index
may be updated with new content, and new commits may be created from the content
stored in the index.
The index is also capable of storing multiple entries (called "stages") for a
given pathname. These stages are used to hold the various unmerged version of a
file when a merge is in progress.
FURTHER DOCUMENTATION
See the references in the "description" section to get started using Git. The
following is probably more detail than necessary for a first-time user.
The [236]Git concepts chapter of the user-manual and [237]gitcore-tutorial(7)
both provide introductions to the underlying Git architecture.
See [238]gitworkflows(7) for an overview of recommended workflows.
See also the [239]howto documents for some useful examples.
The internals are documented in the [240]Git API documentation.
Users migrating from CVS may also want to read [241]gitcvs-migration(7).
Authors
Git was started by Linus Torvalds, and is currently maintained by Junio C Hamano.
Numerous contributions have come from the Git mailing list
. [243]https://openhub.net/p/git/contributors/summary
gives you a more complete list of contributors.
If you have a clone of git.git itself, the output of [244]git-shortlog(1) and
[245]git-blame(1) can show you the authors for specific parts of the project.
Reporting Bugs
Report bugs to the Git mailing list where the
development and maintenance is primarily done. You do not have to be subscribed
to the list to send a message there. See the list archive at
[247]https://lore.kernel.org/git for previous bug reports and other discussions.
Issues which are security relevant should be disclosed privately to the Git
Security mailing list .
SEE ALSO
[249]gittutorial(7), [250]gittutorial-2(7), [251]giteveryday(7),
[252]gitcvs-migration(7), [253]gitglossary(7), [254]gitcore-tutorial(7),
[255]gitcli(7), [256]The Git User's Manual, [257]gitworkflows(7)
GIT
Part of the [258]git(1) suite
____________________________________________________________________________
Last updated 2024-03-25 17:24:49 PDT
References
1. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gittutorial.html
2. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/giteveryday.html
3. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/user-manual.html
4. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcli.html
5. https://git.github.io/htmldocs/git.html
6. https://git-scm.com/docs
7. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-version.html
8. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-help.html
9. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
10. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitnamespaces.html
11. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-replace.html
12. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitattributes.html
13. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-add.html
14. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-am.html
15. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-archive.html
16. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-bisect.html
17. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-branch.html
18. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-bundle.html
19. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-checkout.html
20. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cherry-pick.html
21. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-citool.html
22. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-clean.html
23. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-clone.html
24. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-commit.html
25. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-describe.html
26. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diff.html
27. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fetch.html
28. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-format-patch.html
29. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-gc.html
30. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-grep.html
31. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-gui.html
32. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-init.html
33. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-log.html
34. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-maintenance.html
35. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge.html
36. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mv.html
37. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-notes.html
38. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-pull.html
39. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-push.html
40. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-range-diff.html
41. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rebase.html
42. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-reset.html
43. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-restore.html
44. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-revert.html
45. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rm.html
46. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-shortlog.html
47. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-show.html
48. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-sparse-checkout.html
49. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-stash.html
50. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-status.html
51. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-submodule.html
52. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-switch.html
53. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-tag.html
54. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-worktree.html
55. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitk.html
56. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/scalar.html
57. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
58. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fast-export.html
59. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fast-import.html
60. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-filter-branch.html
61. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mergetool.html
62. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-pack-refs.html
63. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-prune.html
64. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-reflog.html
65. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-remote.html
66. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-repack.html
67. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-replace.html
68. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-annotate.html
69. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-blame.html
70. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-bugreport.html
71. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-count-objects.html
72. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diagnose.html
73. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-difftool.html
74. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fsck.html
75. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-help.html
76. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-instaweb.html
77. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge-tree.html
78. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rerere.html
79. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-show-branch.html
80. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-verify-commit.html
81. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-verify-tag.html
82. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-version.html
83. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-whatchanged.html
84. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitweb.html
85. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-archimport.html
86. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cvsexportcommit.html
87. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cvsimport.html
88. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cvsserver.html
89. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-imap-send.html
90. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-p4.html
91. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-quiltimport.html
92. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-request-pull.html
93. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-send-email.html
94. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-svn.html
95. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-revert.html
96. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-restore.html
97. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-reset.html
98. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-update-index.html
99. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-read-tree.html
100. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-apply.html
101. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-checkout-index.html
102. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-commit-graph.html
103. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-commit-tree.html
104. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-hash-object.html
105. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-index-pack.html
106. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge-file.html
107. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge-index.html
108. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mktag.html
109. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mktree.html
110. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-multi-pack-index.html
111. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-pack-objects.html
112. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-prune-packed.html
113. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-read-tree.html
114. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-replay.html
115. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-symbolic-ref.html
116. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-unpack-objects.html
117. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-update-index.html
118. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-update-ref.html
119. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-write-tree.html
120. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cat-file.html
121. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-cherry.html
122. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diff-files.html
123. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diff-index.html
124. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diff-tree.html
125. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-for-each-ref.html
126. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-for-each-repo.html
127. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-get-tar-commit-id.html
128. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-ls-files.html
129. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-ls-remote.html
130. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-ls-tree.html
131. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge-base.html
132. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-name-rev.html
133. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-pack-redundant.html
134. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rev-list.html
135. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rev-parse.html
136. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-show-index.html
137. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-show-ref.html
138. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-unpack-file.html
139. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-var.html
140. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-verify-pack.html
141. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-daemon.html
142. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fetch-pack.html
143. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-http-backend.html
144. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-send-pack.html
145. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-update-server-info.html
146. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-http-fetch.html
147. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-http-push.html
148. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-receive-pack.html
149. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-shell.html
150. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-upload-archive.html
151. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-upload-pack.html
152. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-check-attr.html
153. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-check-ignore.html
154. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-check-mailmap.html
155. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-check-ref-format.html
156. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-column.html
157. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-credential.html
158. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-credential-cache.html
159. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-credential-store.html
160. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-fmt-merge-msg.html
161. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-hook.html
162. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-interpret-trailers.html
163. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mailinfo.html
164. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-mailsplit.html
165. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge-one-file.html
166. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-patch-id.html
167. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-sh-i18n.html
168. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-sh-setup.html
169. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-stripspace.html
170. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html
171. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcredentials.html
172. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html
173. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitdiffcore.html
174. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/giteveryday.html
175. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitfaq.html
176. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitglossary.html
177. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitnamespaces.html
178. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitremote-helpers.html
179. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitsubmodules.html
180. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gittutorial.html
181. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gittutorial-2.html
182. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitworkflows.html
183. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-help.html
184. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitattributes.html
185. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcli.html
186. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/githooks.html
187. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitignore.html
188. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitmailmap.html
189. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitmodules.html
190. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitrepository-layout.html
191. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitrevisions.html
192. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-help.html
193. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-bundle.html
194. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-chunk.html
195. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-commit-graph.html
196. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-index.html
197. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-pack.html
198. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitformat-signature.html
199. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitprotocol-capabilities.html
200. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitprotocol-common.html
201. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitprotocol-http.html
202. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitprotocol-pack.html
203. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitprotocol-v2.html
204. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
205. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitrevisions.html
206. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitrepository-layout.html
207. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/githooks.html
208. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitglossary.html
209. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-update-index.html
210. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitnamespaces.html
211. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitrepository-layout.html
212. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-worktree.html
213. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-init.html
214. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-init.html
215. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-commit.html
216. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-commit.html
217. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-merge.html
218. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
219. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-var.html
220. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
221. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-rebase.html
222. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
223. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
224. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
225. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/technical/api-trace2.html
226. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/technical/api-trace2.html
227. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/technical/api-trace2.html
228. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-prune.html
229. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
230. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-config.html
231. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-http-backend.html
232. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-checkout.html
233. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-diff.html
234. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/user-manual.html#git-concepts
235. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html
236. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/user-manual.html#git-concepts
237. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html
238. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitworkflows.html
239. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/howto-index.html
240. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/technical/api-index.html
241. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html
242. mailto:git@vger.kernel.org
243. https://openhub.net/p/git/contributors/summary
244. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-shortlog.html
245. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git-blame.html
246. mailto:git@vger.kernel.org
247. https://lore.kernel.org/git
248. mailto:git-security@googlegroups.com
249. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gittutorial.html
250. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gittutorial-2.html
251. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/giteveryday.html
252. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcvs-migration.html
253. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitglossary.html
254. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcore-tutorial.html
255. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitcli.html
256. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/user-manual.html
257. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/gitworkflows.html
258. https://mirrors.edge.kernel.org/pub/software/scm/git/docs/git.html
Usage: http://www.kk-software.de/kklynxview/get/URL
e.g. http://www.kk-software.de/kklynxview/get/http://www.kk-software.de
Errormessages are in German, sorry ;-)