===========================================================
.___ __ __
_________________ __ __ __| _/|__|/ |_
/ ___\_` __ \__ \ | | \/ __ | | \\_ __\
/ /_/ > | \// __ \| | / /_/ | | || |
\___ /|__| (____ /____/\____ | |__||__|
/_____/ \/ \/
grep rough audit - static analysis tool
v2.8 written by @Wireghoul
=================================[justanotherhacker.com]===
git-2.29.2+next.20201030/.github/workflows/main.yml-64- if (head_sha === run.head_sha) {
git-2.29.2+next.20201030/.github/workflows/main.yml:65: core.warning(`Successful run for the commit ${head_sha}: ${run.html_url}`);
git-2.29.2+next.20201030/.github/workflows/main.yml-66- core.setOutput('enabled', ' but skip');
##############################################
git-2.29.2+next.20201030/.github/workflows/main.yml-69- if (run.head_commit && tree_id === run.head_commit.tree_id) {
git-2.29.2+next.20201030/.github/workflows/main.yml:70: core.warning(`Successful run for the tree ${tree_id}: ${run.html_url}`);
git-2.29.2+next.20201030/.github/workflows/main.yml-71- core.setOutput('enabled', ' but skip');
##############################################
git-2.29.2+next.20201030/Documentation/CodingGuidelines-624- `GIT_DIR` is specified
git-2.29.2+next.20201030/Documentation/CodingGuidelines:625: `$GIT_DIR/hooks/pre-receive`
git-2.29.2+next.20201030/Documentation/CodingGuidelines-626-
##############################################
git-2.29.2+next.20201030/Documentation/config.txt-7-linkgit:git-worktree[1]) in each repository are used to store the
git-2.29.2+next.20201030/Documentation/config.txt:8:configuration for that repository, and `$HOME/.gitconfig` is used to
git-2.29.2+next.20201030/Documentation/config.txt-9-store a per-user configuration as fallback values for the `.git/config`
##############################################
git-2.29.2+next.20201030/Documentation/config.txt-119-+
git-2.29.2+next.20201030/Documentation/config.txt:120:The .git location may be auto-discovered, or come from `$GIT_DIR`
git-2.29.2+next.20201030/Documentation/config.txt-121-environment variable. If the repository is auto discovered via a .git
##############################################
git-2.29.2+next.20201030/Documentation/config.txt-163-
git-2.29.2+next.20201030/Documentation/config.txt:164: * Symlinks in `$GIT_DIR` are not resolved before matching.
git-2.29.2+next.20201030/Documentation/config.txt-165-
git-2.29.2+next.20201030/Documentation/config.txt-166- * Both the symlink & realpath versions of paths will be matched
git-2.29.2+next.20201030/Documentation/config.txt:167: outside of `$GIT_DIR`. E.g. if ~/git is a symlink to
git-2.29.2+next.20201030/Documentation/config.txt-168- /mnt/storage/git, both `gitdir:~/git` and `gitdir:/mnt/storage/git`
##############################################
git-2.29.2+next.20201030/Documentation/config.txt-204- path = foo.inc ; find "foo.inc" relative to the current file
git-2.29.2+next.20201030/Documentation/config.txt:205: path = ~/foo.inc ; find "foo.inc" in your `$HOME` directory
git-2.29.2+next.20201030/Documentation/config.txt-206-
##############################################
git-2.29.2+next.20201030/Documentation/config.txt-298- tilde expansion happens to such a string: `~/`
git-2.29.2+next.20201030/Documentation/config.txt:299: is expanded to the value of `$HOME`, and `~user/` to the
git-2.29.2+next.20201030/Documentation/config.txt-300- specified user's home directory.
##############################################
git-2.29.2+next.20201030/Documentation/config/core.txt-317- Enable the reflog. Updates to a ref <ref> is logged to the file
git-2.29.2+next.20201030/Documentation/config/core.txt:318: "`$GIT_DIR/logs/<ref>`", by appending the new and old
git-2.29.2+next.20201030/Documentation/config/core.txt-319- SHA-1, the date/time and the reason of the update, but
git-2.29.2+next.20201030/Documentation/config/core.txt-320- only when the file exists. If this configuration
git-2.29.2+next.20201030/Documentation/config/core.txt:321: variable is set to `true`, missing "`$GIT_DIR/logs/<ref>`"
git-2.29.2+next.20201030/Documentation/config/core.txt-322- file is automatically created for branch heads (i.e. under
##############################################
git-2.29.2+next.20201030/Documentation/config/core.txt-430- to `.gitignore` (per-directory) and `.git/info/exclude`.
git-2.29.2+next.20201030/Documentation/config/core.txt:431: Defaults to `$XDG_CONFIG_HOME/git/ignore`.
git-2.29.2+next.20201030/Documentation/config/core.txt:432: If `$XDG_CONFIG_HOME` is either not set or empty, `$HOME/.config/git/ignore`
git-2.29.2+next.20201030/Documentation/config/core.txt-433- is used instead. See linkgit:gitignore[5].
##############################################
git-2.29.2+next.20201030/Documentation/config/core.txt-448- way as for `core.excludesFile`. Its default value is
git-2.29.2+next.20201030/Documentation/config/core.txt:449: `$XDG_CONFIG_HOME/git/attributes`. If `$XDG_CONFIG_HOME` is either not
git-2.29.2+next.20201030/Documentation/config/core.txt:450: set or empty, `$HOME/.config/git/attributes` is used instead.
git-2.29.2+next.20201030/Documentation/config/core.txt-451-
##############################################
git-2.29.2+next.20201030/Documentation/config/core.txt-453- By default Git will look for your hooks in the
git-2.29.2+next.20201030/Documentation/config/core.txt:454: `$GIT_DIR/hooks` directory. Set this to different path,
git-2.29.2+next.20201030/Documentation/config/core.txt-455- e.g. `/etc/git/hooks`, and Git will try to find your hooks in
git-2.29.2+next.20201030/Documentation/config/core.txt-456- that directory, e.g. `/etc/git/hooks/pre-receive` instead of
git-2.29.2+next.20201030/Documentation/config/core.txt:457: in `$GIT_DIR/hooks/pre-receive`.
git-2.29.2+next.20201030/Documentation/config/core.txt-458-+
##############################################
git-2.29.2+next.20201030/Documentation/config/core.txt-498- is meant to be interpreted by the shell. The order of preference
git-2.29.2+next.20201030/Documentation/config/core.txt:499: is the `$GIT_PAGER` environment variable, then `core.pager`
git-2.29.2+next.20201030/Documentation/config/core.txt:500: configuration, then `$PAGER`, and then the default chosen at
git-2.29.2+next.20201030/Documentation/config/core.txt-501- compile time (usually 'less').
##############################################
git-2.29.2+next.20201030/Documentation/config/gc.txt-97- period. The value "now" may be used to disable the grace
git-2.29.2+next.20201030/Documentation/config/gc.txt:98: period and prune `$GIT_DIR/worktrees` immediately, or "never"
git-2.29.2+next.20201030/Documentation/config/gc.txt-99- may be used to suppress pruning.
##############################################
git-2.29.2+next.20201030/Documentation/config/gpg.txt-1-gpg.program::
git-2.29.2+next.20201030/Documentation/config/gpg.txt:2: Use this custom program instead of "`gpg`" found on `$PATH` when
git-2.29.2+next.20201030/Documentation/config/gpg.txt-3- making or verifying a PGP signature. The program must support the
git-2.29.2+next.20201030/Documentation/config/gpg.txt-4- same command-line interface as GPG, namely, to verify a detached
git-2.29.2+next.20201030/Documentation/config/gpg.txt:5: signature, "`gpg --verify $signature - <$file`" is run, and the
git-2.29.2+next.20201030/Documentation/config/gpg.txt-6- program is expected to signal a good signature by exiting with
git-2.29.2+next.20201030/Documentation/config/gpg.txt-7- code 0, and to generate an ASCII-armored detached signature, the
git-2.29.2+next.20201030/Documentation/config/gpg.txt:8: standard input of "`gpg -bsau $key`" is fed with the contents to be
git-2.29.2+next.20201030/Documentation/config/gpg.txt-9- signed, and the program is expected to send the result to its
##############################################
git-2.29.2+next.20201030/Documentation/config/push.txt-80-repository) to clear the values inherited from a lower priority
git-2.29.2+next.20201030/Documentation/config/push.txt:81:configuration files (e.g. `$HOME/.gitconfig`).
git-2.29.2+next.20201030/Documentation/config/push.txt-82-+
##############################################
git-2.29.2+next.20201030/Documentation/config/rerere.txt-10- enabled if there is an `rr-cache` directory under the
git-2.29.2+next.20201030/Documentation/config/rerere.txt:11: `$GIT_DIR`, e.g. if "rerere" was previously used in the
git-2.29.2+next.20201030/Documentation/config/rerere.txt-12- repository.
##############################################
git-2.29.2+next.20201030/Documentation/fetch-options.txt-69- Write the list of remote refs fetched in the `FETCH_HEAD`
git-2.29.2+next.20201030/Documentation/fetch-options.txt:70: file directly under `$GIT_DIR`. This is the default.
git-2.29.2+next.20201030/Documentation/fetch-options.txt-71- Passing `--no-write-fetch-head` from the command line tells
##############################################
git-2.29.2+next.20201030/Documentation/git-archive.txt-151-option. Alternatively you can keep necessary attributes that should apply
git-2.29.2+next.20201030/Documentation/git-archive.txt:152:while archiving any tree in your `$GIT_DIR/info/attributes` file.
git-2.29.2+next.20201030/Documentation/git-archive.txt-153-
##############################################
git-2.29.2+next.20201030/Documentation/git-check-mailmap.txt-17-
git-2.29.2+next.20201030/Documentation/git-check-mailmap.txt:18:For each ``Name $$<user@host>$$'' or ``$$<user@host>$$'' from the command-line
git-2.29.2+next.20201030/Documentation/git-check-mailmap.txt-19-or standard input (when using `--stdin`), look up the person's canonical name
##############################################
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt-23-a tag is stored in the `refs/tags` hierarchy of the ref namespace
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt:24:(typically in `$GIT_DIR/refs/heads` and `$GIT_DIR/refs/tags`
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt:25:directories or, as entries in file `$GIT_DIR/packed-refs`
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt-26-if refs are packed by `git gc`).
##############################################
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt-83-previous checkout syntax that may refer to a detached HEAD state.
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt:84:The rule `git check-ref-format --branch $name` implements
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt:85:may be stricter than what `git check-ref-format refs/heads/$name`
git-2.29.2+next.20201030/Documentation/git-check-ref-format.txt-86-says (e.g. a dash may appear at the beginning of a ref component,
##############################################
git-2.29.2+next.20201030/Documentation/git-checkout.txt-239- update only entries matched by `<paths>` and sparse patterns
git-2.29.2+next.20201030/Documentation/git-checkout.txt:240: in `$GIT_DIR/info/sparse-checkout`. This option ignores
git-2.29.2+next.20201030/Documentation/git-checkout.txt-241- the sparse patterns and adds back any files in `<paths>`.
##############################################
git-2.29.2+next.20201030/Documentation/git-clone.txt-151- files in `<directory>/.git`, make the `<directory>`
git-2.29.2+next.20201030/Documentation/git-clone.txt:152: itself the `$GIT_DIR`. This obviously implies the `--no-checkout`
git-2.29.2+next.20201030/Documentation/git-clone.txt-153- because there is nowhere to check out the working tree.
##############################################
git-2.29.2+next.20201030/Documentation/git-commit.txt-522-
git-2.29.2+next.20201030/Documentation/git-commit.txt:523:`$GIT_DIR/COMMIT_EDITMSG`::
git-2.29.2+next.20201030/Documentation/git-commit.txt-524- This file contains the commit message of a commit in progress.
##############################################
git-2.29.2+next.20201030/Documentation/git-config.txt-108- rather than the repository `.git/config`, write to
git-2.29.2+next.20201030/Documentation/git-config.txt:109: `$XDG_CONFIG_HOME/git/config` file if this file exists and the
git-2.29.2+next.20201030/Documentation/git-config.txt-110- `~/.gitconfig` file doesn't.
##############################################
git-2.29.2+next.20201030/Documentation/git-config.txt-112-For reading options: read only from global `~/.gitconfig` and from
git-2.29.2+next.20201030/Documentation/git-config.txt:113:`$XDG_CONFIG_HOME/git/config` rather than from all available files.
git-2.29.2+next.20201030/Documentation/git-config.txt-114-+
##############################################
git-2.29.2+next.20201030/Documentation/git-config.txt-118- For writing options: write to system-wide
git-2.29.2+next.20201030/Documentation/git-config.txt:119: `$(prefix)/etc/gitconfig` rather than the repository
git-2.29.2+next.20201030/Documentation/git-config.txt-120- `.git/config`.
git-2.29.2+next.20201030/Documentation/git-config.txt-121-+
git-2.29.2+next.20201030/Documentation/git-config.txt:122:For reading options: read only from system-wide `$(prefix)/etc/gitconfig`
git-2.29.2+next.20201030/Documentation/git-config.txt-123-rather than from all available files.
##############################################
git-2.29.2+next.20201030/Documentation/git-config.txt-180- above.
git-2.29.2+next.20201030/Documentation/git-config.txt:181:- 'path': canonicalize by adding a leading `~` to the value of `$HOME` and
git-2.29.2+next.20201030/Documentation/git-config.txt-182- `~user` to the home directory for the specified user. This specifier has no
##############################################
git-2.29.2+next.20201030/Documentation/git-config.txt-284- Second user-specific configuration file. If $XDG_CONFIG_HOME is not set
git-2.29.2+next.20201030/Documentation/git-config.txt:285: or empty, `$HOME/.config/git/config` will be used. Any single-valued
git-2.29.2+next.20201030/Documentation/git-config.txt-286- variable set in this file will be overwritten by whatever is in
##############################################
git-2.29.2+next.20201030/Documentation/git-credential-cache.txt-36- cache daemon if one is not started).
git-2.29.2+next.20201030/Documentation/git-credential-cache.txt:37: Defaults to `$XDG_CACHE_HOME/git/credential/socket` unless
git-2.29.2+next.20201030/Documentation/git-credential-cache.txt-38- `~/.git-credential-cache/` exists in which case
##############################################
git-2.29.2+next.20201030/Documentation/git-credential-store.txt-37- protected. If not specified, credentials will be searched for from
git-2.29.2+next.20201030/Documentation/git-credential-store.txt:38: `~/.git-credentials` and `$XDG_CONFIG_HOME/git/credentials`, and
git-2.29.2+next.20201030/Documentation/git-credential-store.txt-39- credentials will be written to `~/.git-credentials` if it exists, or
git-2.29.2+next.20201030/Documentation/git-credential-store.txt:40: `$XDG_CONFIG_HOME/git/credentials` if it exists and the former does
git-2.29.2+next.20201030/Documentation/git-credential-store.txt-41- not. See also <<FILES>>.
##############################################
git-2.29.2+next.20201030/Documentation/git-credential-store.txt-54- Second user-specific credentials file. If '$XDG_CONFIG_HOME' is not set
git-2.29.2+next.20201030/Documentation/git-credential-store.txt:55: or empty, `$HOME/.config/git/credentials` will be used. Any credentials
git-2.29.2+next.20201030/Documentation/git-credential-store.txt-56- stored in this file will not be used if `~/.git-credentials` has a
##############################################
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt-159-+
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt:160:For convenience, this data is saved to `$GIT_DIR/cvs-authors`
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt-161-each time the '-A' option is provided and read from that same
##############################################
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt-168--R::
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt:169: Generate a `$GIT_DIR/cvs-revisions` file containing a mapping from CVS
git-2.29.2+next.20201030/Documentation/git-cvsimport.txt-170- revision numbers to newly-created Git commit IDs. The generated file
##############################################
git-2.29.2+next.20201030/Documentation/git-daemon.txt-175-Like many programs that switch user id, the daemon does not reset
git-2.29.2+next.20201030/Documentation/git-daemon.txt:176:environment variables such as `$HOME` when it runs git programs,
git-2.29.2+next.20201030/Documentation/git-daemon.txt-177-e.g. `upload-pack` and `receive-pack`. When using this option, you
##############################################
git-2.29.2+next.20201030/Documentation/git-daemon.txt-212- exiting with a zero status). It can also look at the $REMOTE_ADDR
git-2.29.2+next.20201030/Documentation/git-daemon.txt:213: and `$REMOTE_PORT` environment variables to learn about the
git-2.29.2+next.20201030/Documentation/git-daemon.txt-214- requestor when making this decision.
##############################################
git-2.29.2+next.20201030/Documentation/git-diff.txt-54-of <commit> and HEAD. `git diff --merge-base A` is equivalent to
git-2.29.2+next.20201030/Documentation/git-diff.txt:55:`git diff $(git merge-base A HEAD)`.
git-2.29.2+next.20201030/Documentation/git-diff.txt-56-
##############################################
git-2.29.2+next.20201030/Documentation/git-diff.txt-71-"before" side. `git diff --merge-base A B` is equivalent to
git-2.29.2+next.20201030/Documentation/git-diff.txt:72:`git diff $(git merge-base A B) B`.
git-2.29.2+next.20201030/Documentation/git-diff.txt-73-
##############################################
git-2.29.2+next.20201030/Documentation/git-diff.txt-94- of both <commit>. `git diff A...B` is equivalent to
git-2.29.2+next.20201030/Documentation/git-diff.txt:95: `git diff $(git merge-base A B) B`. You can omit any one
git-2.29.2+next.20201030/Documentation/git-diff.txt-96- of <commit>, which has the same effect as using HEAD instead.
##############################################
git-2.29.2+next.20201030/Documentation/git-difftool.txt-61-the configured command line will be invoked with the following
git-2.29.2+next.20201030/Documentation/git-difftool.txt:62:variables available: `$LOCAL` is set to the name of the temporary
git-2.29.2+next.20201030/Documentation/git-difftool.txt:63:file containing the contents of the diff pre-image and `$REMOTE`
git-2.29.2+next.20201030/Documentation/git-difftool.txt-64-is set to the name of the temporary file containing the contents
git-2.29.2+next.20201030/Documentation/git-difftool.txt:65:of the diff post-image. `$MERGED` is the name of the file which is
git-2.29.2+next.20201030/Documentation/git-difftool.txt:66:being compared. `$BASE` is provided for compatibility
git-2.29.2+next.20201030/Documentation/git-difftool.txt:67:with custom merge tool commands and has the same value as `$MERGED`.
git-2.29.2+next.20201030/Documentation/git-difftool.txt-68-
##############################################
git-2.29.2+next.20201030/Documentation/git-difftool.txt-84- 'git-difftool' ignores the configured defaults and runs
git-2.29.2+next.20201030/Documentation/git-difftool.txt:85: `$command $LOCAL $REMOTE` when this option is specified.
git-2.29.2+next.20201030/Documentation/git-difftool.txt:86: Additionally, `$BASE` is set in the environment.
git-2.29.2+next.20201030/Documentation/git-difftool.txt-87-
##############################################
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt-76-(with the notable exception of the commit filter, for technical reasons).
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt:77:Prior to that, the `$GIT_COMMIT` environment variable will be set to contain
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt-78-the id of the commit being rewritten. Also, GIT_AUTHOR_NAME,
##############################################
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt-160-+
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt:161:You can also use the `git_commit_non_empty_tree "$@"` instead of
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt:162:`git commit-tree "$@"` if you don't wish to keep commits with a single parent
git-2.29.2+next.20201030/Documentation/git-filter-branch.txt-163-and that makes no change to the tree.
##############################################
git-2.29.2+next.20201030/Documentation/git-for-each-ref.txt-321- eval "$entry"
git-2.29.2+next.20201030/Documentation/git-for-each-ref.txt:322: echo `dirname $ref`
git-2.29.2+next.20201030/Documentation/git-for-each-ref.txt-323-done
##############################################
git-2.29.2+next.20201030/Documentation/git-format-patch.txt-435-When sending a patch this way, most often you are sending your own
git-2.29.2+next.20201030/Documentation/git-format-patch.txt:436:patch, so in addition to the "`From $SHA1 $magic_timestamp`" marker you
git-2.29.2+next.20201030/Documentation/git-format-patch.txt-437-should omit `From:` and `Date:` lines from the patch file. The patch
##############################################
git-2.29.2+next.20201030/Documentation/git-http-backend.txt-67---------
git-2.29.2+next.20201030/Documentation/git-http-backend.txt:68:All of the following examples map `http://$hostname/git/foo/bar.git`
git-2.29.2+next.20201030/Documentation/git-http-backend.txt-69-to `/var/www/git/foo/bar.git`.
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-25-
git-2.29.2+next.20201030/Documentation/git-init.txt:26:If the `$GIT_DIR` environment variable is set then it specifies a path
git-2.29.2+next.20201030/Documentation/git-init.txt-27-to use instead of `./.git` for the base of the repository.
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-29-If the object storage directory is specified via the
git-2.29.2+next.20201030/Documentation/git-init.txt:30:`$GIT_OBJECT_DIRECTORY` environment variable then the sha1 directories
git-2.29.2+next.20201030/Documentation/git-init.txt:31:are created underneath - otherwise the default `$GIT_DIR/objects`
git-2.29.2+next.20201030/Documentation/git-init.txt-32-directory is used.
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-65-
git-2.29.2+next.20201030/Documentation/git-init.txt:66:Instead of initializing the repository as a directory to either `$GIT_DIR` or
git-2.29.2+next.20201030/Documentation/git-init.txt-67-`./.git/`, create a text file there containing the path to the actual
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-83-repository. When specified, the config variable "core.sharedRepository" is
git-2.29.2+next.20201030/Documentation/git-init.txt:84:set so that files and directories under `$GIT_DIR` are created with the
git-2.29.2+next.20201030/Documentation/git-init.txt-85-requested permissions. When not specified, Git will use permissions reported
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-129-Files and directories in the template directory whose name do not start with a
git-2.29.2+next.20201030/Documentation/git-init.txt:130:dot will be copied to the `$GIT_DIR` after it is created.
git-2.29.2+next.20201030/Documentation/git-init.txt-131-
##############################################
git-2.29.2+next.20201030/Documentation/git-init.txt-135-
git-2.29.2+next.20201030/Documentation/git-init.txt:136: - the contents of the `$GIT_TEMPLATE_DIR` environment variable;
git-2.29.2+next.20201030/Documentation/git-init.txt-137-
##############################################
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt-244-+
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt:245:If the command contains the `$ARG` string, this string will be
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt-246-replaced with the <value> part of an existing trailer with the same
##############################################
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt-251-also be executed for each of these arguments. And the <value> part of
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt:252:these arguments, if any, will be used to replace the `$ARG` string in
git-2.29.2+next.20201030/Documentation/git-interpret-trailers.txt-253-the command.
##############################################
git-2.29.2+next.20201030/Documentation/git-mergetool.txt-51-`-t` or `--tool` option or the `merge.tool` configuration
git-2.29.2+next.20201030/Documentation/git-mergetool.txt:52:variable) the configured command line will be invoked with `$BASE`
git-2.29.2+next.20201030/Documentation/git-mergetool.txt-53-set to the name of a temporary file containing the common base for
git-2.29.2+next.20201030/Documentation/git-mergetool.txt:54:the merge, if available; `$LOCAL` set to the name of a temporary
git-2.29.2+next.20201030/Documentation/git-mergetool.txt-55-file containing the contents of the file on the current branch;
git-2.29.2+next.20201030/Documentation/git-mergetool.txt:56:`$REMOTE` set to the name of a temporary file containing the
git-2.29.2+next.20201030/Documentation/git-mergetool.txt:57:contents of the file to be merged, and `$MERGED` set to the name
git-2.29.2+next.20201030/Documentation/git-mergetool.txt-58-of the file to which the merge tool should write the result of the
##############################################
git-2.29.2+next.20201030/Documentation/git-notes.txt-74- second object). This subcommand is equivalent to:
git-2.29.2+next.20201030/Documentation/git-notes.txt:75: `git notes add [-f] -C $(git notes list <from-object>) <to-object>`
git-2.29.2+next.20201030/Documentation/git-notes.txt-76-+
##############################################
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-17-'refs') were stored one file per ref in a (sub)directory
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt:18:under `$GIT_DIR/refs`
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-19-directory. While many branch tips tend to be updated often,
##############################################
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-26-problem by storing the refs in a single file,
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt:27:`$GIT_DIR/packed-refs`. When a ref is missing from the
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt:28:traditional `$GIT_DIR/refs` directory hierarchy, it is looked
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-29-up in this
##############################################
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-32-Subsequent updates to branches always create new files under
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt:33:`$GIT_DIR/refs` directory hierarchy.
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-34-
##############################################
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-58-
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt:59:The command usually removes loose refs under `$GIT_DIR/refs`
git-2.29.2+next.20201030/Documentation/git-pack-refs.txt-60-hierarchy after packing them. This option tells it not to.
##############################################
git-2.29.2+next.20201030/Documentation/git-prune-packed.txt-16------------
git-2.29.2+next.20201030/Documentation/git-prune-packed.txt:17:This program searches the `$GIT_OBJECT_DIRECTORY` for all objects that currently
git-2.29.2+next.20201030/Documentation/git-prune-packed.txt-18-exist in a pack file as well as the independent object directories.
##############################################
git-2.29.2+next.20201030/Documentation/git-pull.txt-159-and if there is not any such variable, the value on the `URL:` line
git-2.29.2+next.20201030/Documentation/git-pull.txt:160:in `$GIT_DIR/remotes/<origin>` is used.
git-2.29.2+next.20201030/Documentation/git-pull.txt-161-
##############################################
git-2.29.2+next.20201030/Documentation/git-pull.txt-165-of the configuration variable `remote.<origin>.fetch` are
git-2.29.2+next.20201030/Documentation/git-pull.txt:166:consulted, and if there aren't any, `$GIT_DIR/remotes/<origin>`
git-2.29.2+next.20201030/Documentation/git-pull.txt-167-is consulted and its `Pull:` lines are used.
##############################################
git-2.29.2+next.20201030/Documentation/git-pull.txt-189-uses the refspec from the configuration or
git-2.29.2+next.20201030/Documentation/git-pull.txt:190:`$GIT_DIR/remotes/<origin>`. In such cases, the following
git-2.29.2+next.20201030/Documentation/git-pull.txt-191-rules apply:
##############################################
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt-48-The default for the patch directory is patches
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt:49:or the value of the `$QUILT_PATCHES` environment
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt-50-variable.
##############################################
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt-55-The default for the series file is <patches>/series
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt:56:or the value of the `$QUILT_SERIES` environment
git-2.29.2+next.20201030/Documentation/git-quiltimport.txt-57-variable.
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-106---index-output=<file>::
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:107: Instead of writing the results out to `$GIT_INDEX_FILE`,
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-108- write the resulting index in the named file. While the
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-166-
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:167:Typically, this is invoked as `git read-tree -m $H $M`, where $H
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-168-is the head commit of the current repository, and $M is the head
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-179-
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:180:In this case, the `git read-tree -m $H $M` command makes sure
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-181-that no local change is lost as the result of this "merge".
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-233-see which of the "local changes" that you made were carried forward by running
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:234:`git diff-index --cached $M`. Note that this does not
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:235:necessarily match what `git diff-index --cached $H` would have
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-236-produced before such a two tree merge. This is because of cases
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-239---cached $H` would have told you about the change before this
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:240:merge, but it would not show in `git diff-index --cached $M`
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-241-output after the two-tree merge.
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-364-----------------
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:365:$ git read-tree -m -u `git merge-base $JC $LT` $JC $LT
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-366-$ git merge-index git-merge-one-file -a
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-398-checkout'...) can help maintaining the skip-worktree bitmap and working
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:399:directory update. `$GIT_DIR/info/sparse-checkout` is used to
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-400-define the skip-worktree reference bitmap. When 'git read-tree' needs
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-409-
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:410:While `$GIT_DIR/info/sparse-checkout` is usually used to specify what
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-411-files are in, you can also specify what files are _not_ in, using
##############################################
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-422-directory is still sparsely populated. You should re-populate the working
git-2.29.2+next.20201030/Documentation/git-read-tree.txt:423:directory with the `$GIT_DIR/info/sparse-checkout` file content as
git-2.29.2+next.20201030/Documentation/git-read-tree.txt-424-follows:
##############################################
git-2.29.2+next.20201030/Documentation/git-rebase.txt-946-The "exec" command launches the command in a shell (the one specified
git-2.29.2+next.20201030/Documentation/git-rebase.txt:947:in `$SHELL`, or the default shell if `$SHELL` is not set), so you can
git-2.29.2+next.20201030/Documentation/git-rebase.txt-948-use shell features (like "cd", ">", ";" ...). The command is run from
##############################################
git-2.29.2+next.20201030/Documentation/git-receive-pack.txt-226-When `receive-pack` takes in objects, they are placed into a temporary
git-2.29.2+next.20201030/Documentation/git-receive-pack.txt:227:"quarantine" directory within the `$GIT_DIR/objects` directory and
git-2.29.2+next.20201030/Documentation/git-receive-pack.txt-228-migrated into the main object store only after the `pre-receive` hook
##############################################
git-2.29.2+next.20201030/Documentation/git-remote.txt-88-In case <old> and <new> are the same, and <old> is a file under
git-2.29.2+next.20201030/Documentation/git-remote.txt:89:`$GIT_DIR/remotes` or `$GIT_DIR/branches`, the remote is converted to
git-2.29.2+next.20201030/Documentation/git-remote.txt-90-the configuration file format.
##############################################
git-2.29.2+next.20201030/Documentation/git-replace.txt-91- commit. Use `--convert-graft-file` to convert a
git-2.29.2+next.20201030/Documentation/git-replace.txt:92: `$GIT_DIR/info/grafts` file and use replace refs instead.
git-2.29.2+next.20201030/Documentation/git-replace.txt-93-
git-2.29.2+next.20201030/Documentation/git-replace.txt-94---convert-graft-file::
git-2.29.2+next.20201030/Documentation/git-replace.txt:95: Creates graft commits for all entries in `$GIT_DIR/info/grafts`
git-2.29.2+next.20201030/Documentation/git-replace.txt-96- and deletes that file upon success. The purpose is to help users
##############################################
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-106-you require, you can add the `^{type}` peeling operator to the parameter.
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:107:For example, `git rev-parse "$VAR^{commit}"` will make sure `$VAR`
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-108-names an existing object that is a commit-ish (i.e. a commit, or an
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:109:annotated tag that points at a commit). To make sure that `$VAR`
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:110:names an existing object of any type, `git rev-parse "$VAR^{object}"`
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-111-can be used.
##############################################
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-211---git-dir::
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:212: Show `$GIT_DIR` if defined. Otherwise show the path to
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-213- the .git directory. The path shown, when relative, is
##############################################
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-215-+
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:216:If `$GIT_DIR` is not defined and the current directory
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-217-is not detected to lie in a Git repository or work tree
##############################################
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-224---git-common-dir::
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:225: Show `$GIT_COMMON_DIR` if defined, else `$GIT_DIR`.
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-226-
##############################################
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-391-
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt:392:When `"$@"` is `-h` or `--help` in the above example, the following
git-2.29.2+next.20201030/Documentation/git-rev-parse.txt-393-usage text would be shown:
##############################################
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt-99-
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt:100:The `$GIT_DIR/info/sparse-checkout` file is used to define the
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt-101-skip-worktree reference bitmap. When Git updates the working
##############################################
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt-120-
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt:121:While `$GIT_DIR/info/sparse-checkout` is usually used to specify what
git-2.29.2+next.20201030/Documentation/git-sparse-checkout.txt-122-files are included, you can also specify what files are _not_ included,
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-96- Initialize the submodules recorded in the index (which were
git-2.29.2+next.20201030/Documentation/git-submodule.txt:97: added and committed elsewhere) by setting `submodule.$name.url`
git-2.29.2+next.20201030/Documentation/git-submodule.txt-98- in .git/config. It uses the same setting from `.gitmodules` as
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-107-+
git-2.29.2+next.20201030/Documentation/git-submodule.txt:108:When present, it will also copy the value of `submodule.$name.update`.
git-2.29.2+next.20201030/Documentation/git-submodule.txt-109-This command does not alter existing information in .git/config.
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-119- Unregister the given submodules, i.e. remove the whole
git-2.29.2+next.20201030/Documentation/git-submodule.txt:120: `submodule.$name` section from .git/config together with their work
git-2.29.2+next.20201030/Documentation/git-submodule.txt-121- tree. Further calls to `git submodule update`, `git submodule foreach`
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-251- move the git directory of the submodule into its superproject's
git-2.29.2+next.20201030/Documentation/git-submodule.txt:252: `$GIT_DIR/modules` path and then connect the git directory and
git-2.29.2+next.20201030/Documentation/git-submodule.txt-253- its working directory by setting the `core.worktree` and adding
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-359- in the submodule. This is the default behavior, the main use of
git-2.29.2+next.20201030/Documentation/git-submodule.txt:360: this option is to override `submodule.$name.update` when set to
git-2.29.2+next.20201030/Documentation/git-submodule.txt-361- a value other than `checkout`.
git-2.29.2+next.20201030/Documentation/git-submodule.txt:362: If the key `submodule.$name.update` is either not explicitly set or
git-2.29.2+next.20201030/Documentation/git-submodule.txt-363- set to `checkout`, this option is implicit.
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-371- usual conflict resolution tools.
git-2.29.2+next.20201030/Documentation/git-submodule.txt:372: If the key `submodule.$name.update` is set to `merge`, this option is
git-2.29.2+next.20201030/Documentation/git-submodule.txt-373- implicit.
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-380- to resolve these failures with linkgit:git-rebase[1].
git-2.29.2+next.20201030/Documentation/git-submodule.txt:381: If the key `submodule.$name.update` is set to `rebase`, this option is
git-2.29.2+next.20201030/Documentation/git-submodule.txt-382- implicit.
##############################################
git-2.29.2+next.20201030/Documentation/git-submodule.txt-445-of the containing repository is used to find the url of each submodule.
git-2.29.2+next.20201030/Documentation/git-submodule.txt:446:This file should be formatted in the same way as `$GIT_DIR/config`. The key
git-2.29.2+next.20201030/Documentation/git-submodule.txt-447-to each submodule url is "submodule.$name.url". See linkgit:gitmodules[5]
##############################################
git-2.29.2+next.20201030/Documentation/git-update-index.txt-460-across all repositories you use, because you can set the configuration
git-2.29.2+next.20201030/Documentation/git-update-index.txt:461:variable to `true` (or `false`) in your `$HOME/.gitconfig` just once
git-2.29.2+next.20201030/Documentation/git-update-index.txt-462-and have it affect all repositories you touch.
##############################################
git-2.29.2+next.20201030/Documentation/git-update-index.txt-515-across all repositories you use, because you can set the configuration
git-2.29.2+next.20201030/Documentation/git-update-index.txt:516:variable in your `$HOME/.gitconfig` just once and have it affect all
git-2.29.2+next.20201030/Documentation/git-update-index.txt-517-repositories you touch.
##############################################
git-2.29.2+next.20201030/Documentation/git-var.txt-42- interpreted by the shell when it is used. Examples: `~/bin/vi`,
git-2.29.2+next.20201030/Documentation/git-var.txt:43: `$SOME_ENVIRONMENT_VARIABLE`, `"C:\Program Files\Vim\gvim.exe"
git-2.29.2+next.20201030/Documentation/git-var.txt:44: --nofork`. The order of preference is the `$GIT_EDITOR`
git-2.29.2+next.20201030/Documentation/git-var.txt-45- environment variable, then `core.editor` configuration, then
git-2.29.2+next.20201030/Documentation/git-var.txt:46: `$VISUAL`, then `$EDITOR`, and then the default chosen at compile
git-2.29.2+next.20201030/Documentation/git-var.txt-47- time, which is usually 'vi'.
##############################################
git-2.29.2+next.20201030/Documentation/git-var.txt-54- is meant to be interpreted by the shell. The order of preference
git-2.29.2+next.20201030/Documentation/git-var.txt:55: is the `$GIT_PAGER` environment variable, then `core.pager`
git-2.29.2+next.20201030/Documentation/git-var.txt:56: configuration, then `$PAGER`, and then the default chosen at
git-2.29.2+next.20201030/Documentation/git-var.txt-57- compile time (usually 'less').
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-87-then, as a convenience, the new working tree is associated with a branch
git-2.29.2+next.20201030/Documentation/git-worktree.txt:88:(call it `<branch>`) named after `$(basename <path>)`. If `<branch>`
git-2.29.2+next.20201030/Documentation/git-worktree.txt-89-doesn't exist, a new branch based on `HEAD` is automatically created as
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-120-
git-2.29.2+next.20201030/Documentation/git-worktree.txt:121:Prune working tree information in `$GIT_DIR/worktrees`.
git-2.29.2+next.20201030/Documentation/git-worktree.txt-122-
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-253-with `refs/` are shared. Pseudo refs are ones like `HEAD` which are
git-2.29.2+next.20201030/Documentation/git-worktree.txt:254:directly under `$GIT_DIR` instead of inside `$GIT_DIR/refs`. There are
git-2.29.2+next.20201030/Documentation/git-worktree.txt-255-exceptions, however: refs inside `refs/bisect` and `refs/worktree` are not
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-266-`worktrees/bar/refs/bisect/bad` are the same as
git-2.29.2+next.20201030/Documentation/git-worktree.txt:267:`$GIT_COMMON_DIR/worktrees/foo/HEAD` and
git-2.29.2+next.20201030/Documentation/git-worktree.txt:268:`$GIT_COMMON_DIR/worktrees/bar/refs/bisect/bad`.
git-2.29.2+next.20201030/Documentation/git-worktree.txt-269-
git-2.29.2+next.20201030/Documentation/git-worktree.txt:270:To access refs, it's best not to look inside `$GIT_DIR` directly. Instead
git-2.29.2+next.20201030/Documentation/git-worktree.txt-271-use commands such as linkgit:git-rev-parse[1] or linkgit:git-update-ref[1]
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-293-Note that in this file, the exception for `core.bare` and `core.worktree`
git-2.29.2+next.20201030/Documentation/git-worktree.txt:294:is gone. If they exist in `$GIT_DIR/config`, you must move
git-2.29.2+next.20201030/Documentation/git-worktree.txt-295-them to the `config.worktree` of the main working tree. You may also
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-306-Each linked working tree has a private sub-directory in the repository's
git-2.29.2+next.20201030/Documentation/git-worktree.txt:307:`$GIT_DIR/worktrees` directory. The private sub-directory's name is usually
git-2.29.2+next.20201030/Documentation/git-worktree.txt-308-the base name of the linked working tree's path, possibly appended with a
git-2.29.2+next.20201030/Documentation/git-worktree.txt:309:number to make it unique. For example, when `$GIT_DIR=/path/main/.git` the
git-2.29.2+next.20201030/Documentation/git-worktree.txt-310-command `git worktree add /path/other/test-next next` creates the linked
git-2.29.2+next.20201030/Documentation/git-worktree.txt-311-working tree in `/path/other/test-next` and also creates a
git-2.29.2+next.20201030/Documentation/git-worktree.txt:312:`$GIT_DIR/worktrees/test-next` directory (or `$GIT_DIR/worktrees/test-next1`
git-2.29.2+next.20201030/Documentation/git-worktree.txt-313-if `test-next` is already taken).
git-2.29.2+next.20201030/Documentation/git-worktree.txt-314-
git-2.29.2+next.20201030/Documentation/git-worktree.txt:315:Within a linked working tree, `$GIT_DIR` is set to point to this private
git-2.29.2+next.20201030/Documentation/git-worktree.txt-316-directory (e.g. `/path/main/.git/worktrees/test-next` in the example) and
git-2.29.2+next.20201030/Documentation/git-worktree.txt:317:`$GIT_COMMON_DIR` is set to point back to the main working tree's `$GIT_DIR`
git-2.29.2+next.20201030/Documentation/git-worktree.txt-318-(e.g. `/path/main/.git`). These settings are made in a `.git` file located at
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-321-Path resolution via `git rev-parse --git-path` uses either
git-2.29.2+next.20201030/Documentation/git-worktree.txt:322:`$GIT_DIR` or `$GIT_COMMON_DIR` depending on the path. For example, in the
git-2.29.2+next.20201030/Documentation/git-worktree.txt-323-linked working tree `git rev-parse --git-path HEAD` returns
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-326-rev-parse --git-path refs/heads/master` uses
git-2.29.2+next.20201030/Documentation/git-worktree.txt:327:`$GIT_COMMON_DIR` and returns `/path/main/.git/refs/heads/master`,
git-2.29.2+next.20201030/Documentation/git-worktree.txt-328-since refs are shared across all working trees, except `refs/bisect` and
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-332-thumb is do not make any assumption about whether a path belongs to
git-2.29.2+next.20201030/Documentation/git-worktree.txt:333:`$GIT_DIR` or `$GIT_COMMON_DIR` when you need to directly access something
git-2.29.2+next.20201030/Documentation/git-worktree.txt:334:inside `$GIT_DIR`. Use `git rev-parse --git-path` to get the final path.
git-2.29.2+next.20201030/Documentation/git-worktree.txt-335-
##############################################
git-2.29.2+next.20201030/Documentation/git-worktree.txt-343-
git-2.29.2+next.20201030/Documentation/git-worktree.txt:344:To prevent a `$GIT_DIR/worktrees` entry from being pruned (which
git-2.29.2+next.20201030/Documentation/git-worktree.txt-345-can be useful in some situations, such as when the
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-187- parse-options), main (all commands in libexec directory),
git-2.29.2+next.20201030/Documentation/git.txt:188: others (all other commands in `$PATH` that have git- prefix),
git-2.29.2+next.20201030/Documentation/git.txt-189- list-<category> (see categories in command-list.txt),
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-405-Higher level SCMs may provide and manage additional information in the
git-2.29.2+next.20201030/Documentation/git.txt:406:`$GIT_DIR`.
git-2.29.2+next.20201030/Documentation/git.txt-407-
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-425- This environment allows the specification of an alternate
git-2.29.2+next.20201030/Documentation/git.txt:426: index file. If not specified, the default of `$GIT_DIR/index`
git-2.29.2+next.20201030/Documentation/git.txt-427- is used.
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-437- environment variable then the sha1 directories are created
git-2.29.2+next.20201030/Documentation/git.txt:438: underneath - otherwise the default `$GIT_DIR/objects`
git-2.29.2+next.20201030/Documentation/git.txt-439- directory is used.
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-593-`GIT_PAGER`::
git-2.29.2+next.20201030/Documentation/git.txt:594: This environment variable overrides `$PAGER`. If it is set
git-2.29.2+next.20201030/Documentation/git.txt-595- to an empty string or to the value "cat", Git will not launch
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-603-`GIT_EDITOR`::
git-2.29.2+next.20201030/Documentation/git.txt:604: This environment variable overrides `$EDITOR` and `$VISUAL`.
git-2.29.2+next.20201030/Documentation/git.txt-605- It is used by several Git commands when, on interactive mode,
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-623-+
git-2.29.2+next.20201030/Documentation/git.txt:624:`$GIT_SSH_COMMAND` takes precedence over `$GIT_SSH`, and is interpreted
git-2.29.2+next.20201030/Documentation/git.txt-625-by the shell, which allows additional arguments to be included.
git-2.29.2+next.20201030/Documentation/git.txt:626:`$GIT_SSH` on the other hand must be just the path to a program
git-2.29.2+next.20201030/Documentation/git.txt-627-(which can be a wrapper shell script, if additional arguments are
##############################################
git-2.29.2+next.20201030/Documentation/git.txt-652- Whether to skip reading settings from the system-wide
git-2.29.2+next.20201030/Documentation/git.txt:653: `$(prefix)/etc/gitconfig` file. This environment variable can
git-2.29.2+next.20201030/Documentation/git.txt:654: be used along with `$HOME` and `$XDG_CONFIG_HOME` to create a
git-2.29.2+next.20201030/Documentation/git.txt-655- predictable environment for a picky script, or you can set it
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-70-When deciding what attributes are assigned to a path, Git
git-2.29.2+next.20201030/Documentation/gitattributes.txt:71:consults `$GIT_DIR/info/attributes` file (which has the highest
git-2.29.2+next.20201030/Documentation/gitattributes.txt-72-precedence), `.gitattributes` file in the same directory as the
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-86-one user's workflow for that repository), then
git-2.29.2+next.20201030/Documentation/gitattributes.txt:87:attributes should be placed in the `$GIT_DIR/info/attributes` file.
git-2.29.2+next.20201030/Documentation/gitattributes.txt-88-Attributes which should be version-controlled and distributed to other
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-95-Attributes for all users on a system should be placed in the
git-2.29.2+next.20201030/Documentation/gitattributes.txt:96:`$(prefix)/etc/gitattributes` file.
git-2.29.2+next.20201030/Documentation/gitattributes.txt-97-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-378-When the attribute `ident` is set for a path, Git replaces
git-2.29.2+next.20201030/Documentation/gitattributes.txt:379:`$Id$` in the blob object with `$Id:`, followed by the
git-2.29.2+next.20201030/Documentation/gitattributes.txt-380-40-character hexadecimal blob object name, followed by a dollar
git-2.29.2+next.20201030/Documentation/gitattributes.txt-381-sign `$` upon checkout. Any byte sequence that begins with
git-2.29.2+next.20201030/Documentation/gitattributes.txt:382:`$Id:` and ends with `$` in the worktree file is replaced
git-2.29.2+next.20201030/Documentation/gitattributes.txt:383:with `$Id$` upon check-in.
git-2.29.2+next.20201030/Documentation/gitattributes.txt-384-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-745-To define an external diff driver `jcdiff`, add a section to your
git-2.29.2+next.20201030/Documentation/gitattributes.txt:746:`$GIT_DIR/config` file (or `$HOME/.gitconfig` file) like this:
git-2.29.2+next.20201030/Documentation/gitattributes.txt-747-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-783-want to appear as the hunk header "TEXT". Add a section to your
git-2.29.2+next.20201030/Documentation/gitattributes.txt:784:`$GIT_DIR/config` file (or `$HOME/.gitconfig` file) like this:
git-2.29.2+next.20201030/Documentation/gitattributes.txt-785-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-859-whitespace. To separate them, use a regular expression in your
git-2.29.2+next.20201030/Documentation/gitattributes.txt:860:`$GIT_DIR/config` file (or `$HOME/.gitconfig` file) like this:
git-2.29.2+next.20201030/Documentation/gitattributes.txt-861-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-888-exif tool installed), add the following section to your
git-2.29.2+next.20201030/Documentation/gitattributes.txt:889:`$GIT_DIR/config` file (or `$HOME/.gitconfig` file):
git-2.29.2+next.20201030/Documentation/gitattributes.txt-890-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1071-To define a custom merge driver `filfre`, add a section to your
git-2.29.2+next.20201030/Documentation/gitattributes.txt:1072:`$GIT_DIR/config` file (or `$HOME/.gitconfig` file) like this:
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1073-
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1174-as those for the option `--pretty=format:` of linkgit:git-log[1],
git-2.29.2+next.20201030/Documentation/gitattributes.txt:1175:except that they need to be wrapped like this: `$Format:PLACEHOLDERS$`
git-2.29.2+next.20201030/Documentation/gitattributes.txt:1176:in the file. E.g. the string `$Format:%H$` will be replaced by the
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1177-commit hash.
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1236-Custom macro attributes can be defined only in top-level gitattributes
git-2.29.2+next.20201030/Documentation/gitattributes.txt:1237:files (`$GIT_DIR/info/attributes`, the `.gitattributes` file at the
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1238-top level of the working tree, or the global or system-wide
##############################################
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1287-
git-2.29.2+next.20201030/Documentation/gitattributes.txt:1288:3. Finally it examines `$GIT_DIR/info/attributes`. This file
git-2.29.2+next.20201030/Documentation/gitattributes.txt-1289- is used to override the in-tree settings. The first line is
##############################################
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1315-you need to make sure that you have the 'git-receive-pack'
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt:1316:program on the `$PATH`.
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1317-
##############################################
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1322-`.bash_profile`. As a workaround, make sure `.bashrc` sets up
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt:1323:`$PATH` so that you can run 'git-receive-pack' program.
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1324-
##############################################
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1447-'dumb transport friendly'. After `git init`,
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt:1448:`$GIT_DIR/hooks/post-update.sample` copied from the standard templates
git-2.29.2+next.20201030/Documentation/gitcore-tutorial.txt-1449-would contain a call to 'git update-server-info'
##############################################
git-2.29.2+next.20201030/Documentation/gitcredentials.txt-243-users by naming their program "git-credential-$NAME", and putting it in
git-2.29.2+next.20201030/Documentation/gitcredentials.txt:244:the `$PATH` or `$GIT_EXEC_PATH` during installation, which will allow a
git-2.29.2+next.20201030/Documentation/gitcredentials.txt:245:user to enable it with `git config credential.helper $NAME`.
git-2.29.2+next.20201030/Documentation/gitcredentials.txt-246-
##############################################
git-2.29.2+next.20201030/Documentation/giteveryday.txt-401-e.g. those using:
git-2.29.2+next.20201030/Documentation/giteveryday.txt:402:`$ git push/pull ssh://host.xz/pub/scm/project`
git-2.29.2+next.20201030/Documentation/giteveryday.txt-403-+
##############################################
git-2.29.2+next.20201030/Documentation/gitfaq.txt-344-you'll probably want to make it in a per-user configuration file or in the one
git-2.29.2+next.20201030/Documentation/gitfaq.txt:345:in `$GIT_DIR/info/attributes`, since making it in a `.gitattributes` file in the
git-2.29.2+next.20201030/Documentation/gitfaq.txt-346-repository will apply to all users of the repository.
##############################################
git-2.29.2+next.20201030/Documentation/githooks.txt-19-
git-2.29.2+next.20201030/Documentation/githooks.txt:20:By default the hooks directory is `$GIT_DIR/hooks`, but that can be
git-2.29.2+next.20201030/Documentation/githooks.txt-21-changed via the `core.hooksPath` configuration variable (see
##############################################
git-2.29.2+next.20201030/Documentation/githooks.txt-521-
git-2.29.2+next.20201030/Documentation/githooks.txt:522:For example, the hook can simply run `git read-tree -u -m HEAD "$1"`
git-2.29.2+next.20201030/Documentation/githooks.txt-523-in order to emulate `git fetch` that is run in the reverse direction
##############################################
git-2.29.2+next.20201030/Documentation/gitignore.txt-37-
git-2.29.2+next.20201030/Documentation/gitignore.txt:38: * Patterns read from `$GIT_DIR/info/exclude`.
git-2.29.2+next.20201030/Documentation/gitignore.txt-39-
##############################################
git-2.29.2+next.20201030/Documentation/gitignore.txt-53- the repository but are specific to one user's workflow) should go into
git-2.29.2+next.20201030/Documentation/gitignore.txt:54: the `$GIT_DIR/info/exclude` file.
git-2.29.2+next.20201030/Documentation/gitignore.txt-55-
##############################################
git-2.29.2+next.20201030/Documentation/gitignore.txt-139-file containing patterns of file names to exclude, similar to
git-2.29.2+next.20201030/Documentation/gitignore.txt:140:`$GIT_DIR/info/exclude`. Patterns in the exclude file are used in addition to
git-2.29.2+next.20201030/Documentation/gitignore.txt:141:those in `$GIT_DIR/info/exclude`.
git-2.29.2+next.20201030/Documentation/gitignore.txt-142-
##############################################
git-2.29.2+next.20201030/Documentation/gitk.txt-174-
git-2.29.2+next.20201030/Documentation/gitk.txt:175:* `$XDG_CONFIG_HOME/git/gitk` if it exists, otherwise
git-2.29.2+next.20201030/Documentation/gitk.txt:176:* `$HOME/.gitk` if it exists
git-2.29.2+next.20201030/Documentation/gitk.txt-177-
git-2.29.2+next.20201030/Documentation/gitk.txt:178:If neither of the above exist then `$XDG_CONFIG_HOME/git/gitk` is created and
git-2.29.2+next.20201030/Documentation/gitk.txt-179-used by default. If '$XDG_CONFIG_HOME' is not set it defaults to
git-2.29.2+next.20201030/Documentation/gitk.txt:180:`$HOME/.config` in all cases.
git-2.29.2+next.20201030/Documentation/gitk.txt-181-
##############################################
git-2.29.2+next.20201030/Documentation/gitremote-helpers.txt-305-Optionally may output a 'lock <file>' line indicating the full path of
git-2.29.2+next.20201030/Documentation/gitremote-helpers.txt:306:a file under `$GIT_DIR/objects/pack` which is keeping a pack until
git-2.29.2+next.20201030/Documentation/gitremote-helpers.txt-307-refs can be suitably updated. The path must end with `.keep`. This is
##############################################
git-2.29.2+next.20201030/Documentation/gitrepository-layout.txt-42-. You could be using the `objects/info/alternates` or
git-2.29.2+next.20201030/Documentation/gitrepository-layout.txt:43:`$GIT_ALTERNATE_OBJECT_DIRECTORIES` mechanisms to 'borrow'
git-2.29.2+next.20201030/Documentation/gitrepository-layout.txt-44-objects from other object stores. A repository with this kind
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-23-On the filesystem, a submodule usually (but not always - see FORMS below)
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:24:consists of (i) a Git directory located under the `$GIT_DIR/modules/`
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-25-directory of its superproject, (ii) a working directory inside the
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-28-
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:29:Assuming the submodule has a Git directory at `$GIT_DIR/modules/foo/`
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-30-and a working directory at `path/to/bar/`, the superproject tracks the
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-85-
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:86: * The configuration inside the submodule. This includes `$GIT_DIR/config`
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-87- in the submodule, but also settings in the tree such as a `.gitattributes`
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-96-+
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:97:The submodule's `$GIT_DIR/config` file would come into play when running
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-98-`git push --recurse-submodules=check` in the superproject, as this would
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-99-check if the submodule has any changes not published to any remote. The
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:100:remotes are configured in the submodule as usual in the `$GIT_DIR/config`
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-101-file.
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-102-
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:103: * The configuration file `$GIT_DIR/config` in the superproject.
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-104- Git only recurses into active submodules (see "ACTIVE SUBMODULES"
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-139-When deinitialized or deleted (see below), the submodule's Git
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:140:directory is automatically moved to `$GIT_DIR/modules/<name>/`
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-141-of the superproject.
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-149-Besides emptying the working directory, this command only modifies
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:150:the superproject's `$GIT_DIR/config` file, so the superproject's history
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-151-is not affected. This can be undone using `git submodule init`.
##############################################
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-164-To completely remove a submodule, manually delete
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt:165:`$GIT_DIR/modules/<name>/`.
git-2.29.2+next.20201030/Documentation/gitsubmodules.txt-166-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-16-perl script fragment as its configuration file. You can set variables
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:17:using "`our $variable = value`"; text from a "#" character until the
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-18-end of a line is ignored. See *perlsyn*(1) for details.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-76-gitweb itself is written in). Variables are typically set using the
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:77:`our` qualifier (as in "`our $variable = <value>;`") to avoid syntax
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-78-errors if a new version of gitweb no longer uses a variable and therefore
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-121- Absolute filesystem path which will be prepended to project path;
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:122: the path to repository is `$projectroot/$project`. Set to
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:123: `$GITWEB_PROJECTROOT` during installation. This variable has to be
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-124- set correctly for gitweb to find repositories.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-125-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:126:For example, if `$projectroot` is set to "/srv/git" by putting the following
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-127-in gitweb config file:
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-159-makefile variable at installation time. If this variable is empty, gitweb
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:160:will fall back to scanning the `$projectroot` directory for repositories.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-161-
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-162-$project_maxdepth::
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:163: If `$projects_list` variable is unset, gitweb will recursively
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:164: scan filesystem for Git repositories. The `$project_maxdepth`
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:165: is used to limit traversing depth, relative to `$projectroot`
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-166- (starting point); it means that directories which are further
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:167: from `$projectroot` than `$project_maxdepth` will be skipped.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-168-+
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-196-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:197:though the above might be done by using `$export_ok` instead
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-198-+
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-209- Only allow viewing of repositories also shown on the overview page.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:210: This for example makes `$export_ok` file decide if repository is
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:211: available and not only if it is shown. If `$projects_list` points to
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-212- file with list of project, only those repositories listed would be
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-225-$GIT::
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:226: Core git executable to use. By default set to `$GIT_BINDIR/git`, which
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:227: in turn is by default set to `$(bindir)/git`. If you use Git installed
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-228- from a binary package, you should usually set this to "/usr/bin/git".
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-303-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:304:*Note*: there is also a legacy `$stylesheet` configuration variable, which was
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:305:used by older gitweb. If `$stylesheet` variable is defined, only CSS stylesheet
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-306-given by this variable is used by gitweb.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-338- "breadcrumbs"). By default it is set to the absolute URI of a current page
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:339: (to the value of `$my_uri` variable, or to "/" if `$my_uri` is undefined
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-340- or is an empty string).
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-342-$home_link_str::
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:343: Label for the "home link" at the top of all pages, leading to `$home_link`
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-344- (usually the main gitweb page, which contains the projects list). It is
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-356- server. Each element of the list is a reference to an array, in which
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:357: element 0 is the link text (equivalent to `$home_link_str`) and element
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:358: 1 is the target URL (equivalent to `$home_link`).
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-359-+
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-430- are "none" (unsorted), "project" (projects are by project name,
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:431: i.e. path to repository relative to `$projectroot`), "descr"
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-432- (project description), "owner", and "age" (by date of most current
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-445- Gitweb guesses mimetype of a file to display based on extension
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:446: of its filename, using `$mimetypes_file` (if set and file exists)
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-447- and `/etc/mime.types` files (see *mime.types*(5) manpage; only
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-483- describing from where to fetch a project, which are shown on
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:484: project summary page. The full fetch URL is "`$git_base_url/$project`",
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-485- for each element of this list. You can set up multiple base URLs
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-488-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:489:Note that per repository configuration can be set in `$GIT_DIR/cloneurl`
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-490-file, or as values of multi-value `gitweb.url` configuration variable in
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-501- list page. The category of a project is determined by the
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:502: `$GIT_DIR/category` file or the `gitweb.category` variable in each
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-503- repository's configuration. Disabled by default (set to 0).
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-508- listed at the top, above categorized projects. Used only if project
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:509: categories are enabled, which means if `$projects_list_group_categories`
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-510- is true. By default set to "" (empty string).
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-526-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:527:Set `$maxload` to undefined value (`undef`) to turn this feature off.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-528-The default value is 300.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-548-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:549:If `$per_request_config` is not a code reference, it is interpreted as boolean
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-550-value. If it is true gitweb will process config files once per request,
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-553-+
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:554:*NOTE*: `$my_url`, `$my_uri`, and `$base_url` are overwritten with their default
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-555-values before every request, so if you want to change them, be sure to set
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-587- variables, but now there should be no need to do it. See
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:588: `$per_request_config` if you need to set them still.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-589-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-591- Base URL for relative URLs in pages generated by gitweb,
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:592: (e.g. `$logo`, `$favicon`, `@stylesheets` if they are relative URLs),
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-593- needed and used '<base href="$base_url">' only for URLs with nonempty
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-595- and there is no need to set this variable, e.g. to $my_uri or "/".
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:596: See `$per_request_config` if you need to override it anyway.
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-597-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-755- Server-side syntax highlight support in "blob" view. It requires
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:756: `$highlight_bin` program to be available (see the description of
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-757- this variable in the "Configuration variables" section above),
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-789- shown in the main projects list. Instead, a \'+' mark is shown
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:790: next to `$projname`, which links to a "forks" view that lists all
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:791: the forks (all projects in `$projname/` subdirectory). Additionally
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-792- a "forks" view for a project is linked from project summary page.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-807-expands to the project name, `%f` to the project path within the
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt:808:filesystem (i.e. "$projectroot/$project"), `%h` to the current hash
git-2.29.2+next.20201030/Documentation/gitweb.conf.txt-809-(\'h' gitweb parameter) and `%b` to the current hash base
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-52-
git-2.29.2+next.20201030/Documentation/gitweb.txt:53:The default value for `$projectroot` is `/pub/git`. You can change it during
git-2.29.2+next.20201030/Documentation/gitweb.txt-54-building gitweb via `GITWEB_PROJECTROOT` build configuration variable.
git-2.29.2+next.20201030/Documentation/gitweb.txt-55-
git-2.29.2+next.20201030/Documentation/gitweb.txt:56:By default all Git repositories under `$projectroot` are visible and available
git-2.29.2+next.20201030/Documentation/gitweb.txt-57-to gitweb. The list of projects is generated by default by scanning the
git-2.29.2+next.20201030/Documentation/gitweb.txt:58:`$projectroot` directory for Git repositories (for object databases to be
git-2.29.2+next.20201030/Documentation/gitweb.txt-59-more exact; gitweb is not interested in a working area, and is best suited
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-61-
git-2.29.2+next.20201030/Documentation/gitweb.txt:62:The name of the repository in gitweb is the path to its `$GIT_DIR` (its object
git-2.29.2+next.20201030/Documentation/gitweb.txt:63:database) relative to `$projectroot`. Therefore the repository $repo can be
git-2.29.2+next.20201030/Documentation/gitweb.txt-64-found at "$projectroot/$repo".
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-70-starting from $projectroot, you can provide a pre-generated list of
git-2.29.2+next.20201030/Documentation/gitweb.txt:71:visible projects by setting `$projects_list` to point to a plain text
git-2.29.2+next.20201030/Documentation/gitweb.txt-72-file with a list of projects (with some additional info).
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-81-* Whitespace separated fields; any run of whitespace can be used as field
git-2.29.2+next.20201030/Documentation/gitweb.txt:82:separator (rules for Perl's "`split(" ", $line)`").
git-2.29.2+next.20201030/Documentation/gitweb.txt-83-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-95-<repository path>::
git-2.29.2+next.20201030/Documentation/gitweb.txt:96: path to repository GIT_DIR, relative to `$projectroot`
git-2.29.2+next.20201030/Documentation/gitweb.txt-97-<repository owner>::
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-115-visible on projects list page, you can view it nevertheless by hand-crafting
git-2.29.2+next.20201030/Documentation/gitweb.txt:116:a gitweb URL. By setting `$strict_export` configuration variable (see
git-2.29.2+next.20201030/Documentation/gitweb.txt-117-linkgit:gitweb.conf[5]) to true value you can allow viewing only of
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-133-suitable for GITWEB_LIST build configuration variable (or
git-2.29.2+next.20201030/Documentation/gitweb.txt:134:`$projects_list` variable in gitweb config):
git-2.29.2+next.20201030/Documentation/gitweb.txt-135-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-148-Run this script and save its output to a file. This file could then be used
git-2.29.2+next.20201030/Documentation/gitweb.txt:149:as projects list file, which means that you can set `$projects_list` to its
git-2.29.2+next.20201030/Documentation/gitweb.txt-150-filename.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-154-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
git-2.29.2+next.20201030/Documentation/gitweb.txt:155:By default all Git repositories under `$projectroot` are visible and
git-2.29.2+next.20201030/Documentation/gitweb.txt-156-available to gitweb. You can however configure how gitweb controls access
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-160-projects are *visible* by selectively including repositories in projects
git-2.29.2+next.20201030/Documentation/gitweb.txt:161:list file, and setting `$projects_list` gitweb configuration variable to
git-2.29.2+next.20201030/Documentation/gitweb.txt:162:point to it. With `$strict_export` set, projects list file can be used to
git-2.29.2+next.20201030/Documentation/gitweb.txt-163-control which repositories are *available* as well.
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-165-* You can configure gitweb to only list and allow viewing of the explicitly
git-2.29.2+next.20201030/Documentation/gitweb.txt:166:exported repositories, via `$export_ok` variable in gitweb config file; see
git-2.29.2+next.20201030/Documentation/gitweb.txt-167-linkgit:gitweb.conf[5] manpage. If it evaluates to true, gitweb shows
git-2.29.2+next.20201030/Documentation/gitweb.txt:168:repositories only if this file named by `$export_ok` exists in its object
git-2.29.2+next.20201030/Documentation/gitweb.txt:169:database (if directory has the magic file named `$export_ok`).
git-2.29.2+next.20201030/Documentation/gitweb.txt-170-+
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-217- homepage), etc. This is recognized only if XSS prevention is off
git-2.29.2+next.20201030/Documentation/gitweb.txt:218: (`$prevent_xss` is false, see linkgit:gitweb.conf[5]); a way to include
git-2.29.2+next.20201030/Documentation/gitweb.txt-219- a README safely when XSS prevention is on may be worked out in the
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-222-description (or `gitweb.description`)::
git-2.29.2+next.20201030/Documentation/gitweb.txt:223: Short (shortened to `$projects_list_description_width` in the projects
git-2.29.2+next.20201030/Documentation/gitweb.txt-224- list page, which is 25 characters by default; see
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-237- Singe line category of a project, used to group projects if
git-2.29.2+next.20201030/Documentation/gitweb.txt:238: `$projects_list_group_categories` is enabled. By default (file and
git-2.29.2+next.20201030/Documentation/gitweb.txt-239- configuration variable absent), uncategorized projects are put in the
git-2.29.2+next.20201030/Documentation/gitweb.txt:240: `$project_list_default_category` category. You can use the
git-2.29.2+next.20201030/Documentation/gitweb.txt-241- `gitweb.category` repo configuration variable, but the file takes
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-243-+
git-2.29.2+next.20201030/Documentation/gitweb.txt:244:The configuration variables `$projects_list_group_categories` and
git-2.29.2+next.20201030/Documentation/gitweb.txt:245:`$project_list_default_category` are described in linkgit:gitweb.conf[5]
git-2.29.2+next.20201030/Documentation/gitweb.txt-246-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-262-If it's not set, filesystem directory's owner is used (via GECOS field,
git-2.29.2+next.20201030/Documentation/gitweb.txt:263:i.e. real name field from *getpwuid*(3)) if `$projects_list` is unset
git-2.29.2+next.20201030/Documentation/gitweb.txt:264:(gitweb scans `$projectroot` for repositories); if `$projects_list`
git-2.29.2+next.20201030/Documentation/gitweb.txt-265-points to file with list of repositories, then project owner defaults to
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-581-*Note* that this requires to be set for each request, so either
git-2.29.2+next.20201030/Documentation/gitweb.txt:582:`$per_request_config` must be false, or the above must be put in code
git-2.29.2+next.20201030/Documentation/gitweb.txt:583:referenced by `$per_request_config`;
git-2.29.2+next.20201030/Documentation/gitweb.txt-584-
##############################################
git-2.29.2+next.20201030/Documentation/gitweb.txt-643-*Notice* that in this case you don't need special settings for
git-2.29.2+next.20201030/Documentation/gitweb.txt:644:`@stylesheets`, `$my_uri` and `$home_link`, but you lose "dumb client"
git-2.29.2+next.20201030/Documentation/gitweb.txt-645-access to your project .git dirs (described in "Single URL for gitweb and
##############################################
git-2.29.2+next.20201030/Documentation/glossary-content.txt-189- <<def_branch,branch>>. Heads are stored in a file in
git-2.29.2+next.20201030/Documentation/glossary-content.txt:190: `$GIT_DIR/refs/heads/` directory, except when using packed refs. (See
git-2.29.2+next.20201030/Documentation/glossary-content.txt-191- linkgit:git-pack-refs[1].)
##############################################
git-2.29.2+next.20201030/Documentation/glossary-content.txt-209- operation is done. The hook scripts are found in the
git-2.29.2+next.20201030/Documentation/glossary-content.txt:210: `$GIT_DIR/hooks/` directory, and are enabled by simply
git-2.29.2+next.20201030/Documentation/glossary-content.txt-211- removing the `.sample` suffix from the filename. In earlier versions
##############################################
git-2.29.2+next.20201030/Documentation/glossary-content.txt-262- identified by its <<def_object_name,object name>>. The objects usually
git-2.29.2+next.20201030/Documentation/glossary-content.txt:263: live in `$GIT_DIR/objects/`.
git-2.29.2+next.20201030/Documentation/glossary-content.txt-264-
##############################################
git-2.29.2+next.20201030/Documentation/glossary-content.txt-454-[[def_pseudoref]]pseudoref::
git-2.29.2+next.20201030/Documentation/glossary-content.txt:455: Pseudorefs are a class of files under `$GIT_DIR` which behave
git-2.29.2+next.20201030/Documentation/glossary-content.txt-456- like refs for the purposes of rev-parse, but which are treated
##############################################
git-2.29.2+next.20201030/Documentation/lint-gitlink.perl-32- while (<$fh>) {
git-2.29.2+next.20201030/Documentation/lint-gitlink.perl:33: my $where = "$file:$.";
git-2.29.2+next.20201030/Documentation/lint-gitlink.perl-34- while (s/linkgit:((.*?)\[(\d)\])//) {
##############################################
git-2.29.2+next.20201030/Documentation/merge-options.txt-94- happened (except for the merge information), but do not actually
git-2.29.2+next.20201030/Documentation/merge-options.txt:95: make a commit, move the `HEAD`, or record `$GIT_DIR/MERGE_HEAD`
git-2.29.2+next.20201030/Documentation/merge-options.txt-96- (to cause the next `git commit` command to create a merge
##############################################
git-2.29.2+next.20201030/Documentation/rev-list-options.txt-907-Besides the '{plus}' and '%' characters, the following characters are
git-2.29.2+next.20201030/Documentation/rev-list-options.txt:908:reserved and also must be encoded: `~!@#$^&*()[]{}\;",<>?`+'`+
git-2.29.2+next.20201030/Documentation/rev-list-options.txt-909-as well as all characters with ASCII code <= `0x20`, which includes
##############################################
git-2.29.2+next.20201030/Documentation/revisions.txt-60-Note that any of the 'refs/*' cases above may come either from
git-2.29.2+next.20201030/Documentation/revisions.txt:61:the `$GIT_DIR/refs` directory or from the `$GIT_DIR/packed-refs` file.
git-2.29.2+next.20201030/Documentation/revisions.txt-62-While the ref name encoding is unspecified, UTF-8 is preferred as
##############################################
git-2.29.2+next.20201030/Documentation/technical/api-parse-options.txt-227-
git-2.29.2+next.20201030/Documentation/technical/api-parse-options.txt:228:`OPT_PASSTHRU(short, long, &char_var, arg_str, description, flags)`::
git-2.29.2+next.20201030/Documentation/technical/api-parse-options.txt-229- Introduce an option that will be reconstructed into a char* string,
##############################################
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-142-to organize these files. Each commit-graph file has a name
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt:143:`$OBJDIR/info/commit-graphs/graph-{hash}.graph` where `{hash}` is the hex-
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-144-valued hash stored in the footer of that file (which is a hash of the file's
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-145-contents before that hash). For a chain of commit-graph files, a plain-text
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt:146:file at `$OBJDIR/info/commit-graphs/commit-graph-chain` contains the
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-147-hashes for the files in order from "lowest" to "highest".
##############################################
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-279-we update the modified times of the files when they become unreferenced. Then,
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt:280:we scan the `$OBJDIR/info/commit-graphs/` directory for `graph-{hash}`
git-2.29.2+next.20201030/Documentation/technical/commit-graph.txt-281-files whose modified times are older than a given expiry window. This window
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-22-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:23:Within this documentation the placeholder `$GIT_URL` will stand for
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-24-the http:// repository URL entered by the end-user.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-25-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:26:Servers SHOULD handle all requests to locations matching `$GIT_URL`, as
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-27-both the "smart" and "dumb" HTTP protocols used by Git operate
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-28-by appending additional path components onto the end of the user
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:29:supplied `$GIT_URL` string.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-30-
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-46-Clients MUST strip a trailing `/`, if present, from the user supplied
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:47:`$GIT_URL` string to prevent empty path tokens (`//`) from appearing
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-48-in any URL sent to a server. Compatible clients MUST expand
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:49:`$GIT_URL/info/refs` as `foo/info/refs` and not `foo//info/refs`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-50-
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-105-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:106:If there is no repository at `$GIT_URL`, or the resource pointed to by a
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:107:location matching `$GIT_URL` does not exist, the server MUST NOT respond
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-108-with `200 OK` response. A server SHOULD respond with
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-111-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:112:If there is a repository at `$GIT_URL`, but access is not currently
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-113-permitted, the server MUST respond with the `403 Forbidden` HTTP
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-150-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:151:Dumb HTTP clients MUST make a `GET` request to `$GIT_URL/info/refs`,
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-152-without any search/query parameters.
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-194-The request MUST contain exactly one query parameter,
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:195:`service=$servicename`, where `$servicename` MUST be the service
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-196-name the client wishes to contact to complete the operation.
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-246-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:247:The Content-Type MUST be `application/x-$servicename-advertisement`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-248-Clients SHOULD fall back to the dumb protocol if another content
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-249-type is returned. When falling back to the dumb protocol clients
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:250:SHOULD NOT make an additional request to `$GIT_URL/info/refs`, but
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-251-instead SHOULD use the response already in hand. Clients MUST NOT
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-263-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:264:Clients MUST verify the first pkt-line is `# service=$servicename`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-265-Servers MUST set $servicename to be the request parameter value.
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-304-------------------------------
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:305:This service reads from the repository pointed to by `$GIT_URL`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-306-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-307-Clients MUST first perform ref discovery with
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:308:`$GIT_URL/info/refs?service=git-upload-pack`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-309-
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-374-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:375:C: Send one `$GIT_URL/git-upload-pack` request:
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-376-
##############################################
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-468-------------------------------
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:469:This service reads from the repository pointed to by `$GIT_URL`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-470-
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-471-Clients MUST first perform ref discovery with
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt:472:`$GIT_URL/info/refs?service=git-receive-pack`.
git-2.29.2+next.20201030/Documentation/technical/http-protocol.txt-473-
##############################################
git-2.29.2+next.20201030/Documentation/technical/protocol-v2.txt-81-Subsequent requests are then made directly to the service
git-2.29.2+next.20201030/Documentation/technical/protocol-v2.txt:82:`$GIT_URL/git-upload-pack`. (This works the same for git-receive-pack).
git-2.29.2+next.20201030/Documentation/technical/protocol-v2.txt-83-
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-24-due to the larger number of syscalls required to traverse and read the
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:25:`$GIT_DIR/refs` directory.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-26-
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-139-This property is useful for retaining log records in reftable, but may
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:140:confuse versions of Git using `$GIT_DIR/refs` directory tree to maintain
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-141-references. Users of reftable may choose to continue to reject `foo` and
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-675-
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:676:When importing from `$GIT_DIR/logs` writers should globally order all
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-677-log records roughly by timestamp while preserving file order, and assign
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-862-
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:863:A repository must set its `$GIT_DIR/config` to configure reftable:
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-864-
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-874-
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:875:A collection of reftable files are stored in the `$GIT_DIR/reftable/`
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-876-directory:
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-884-where reftable files are named by a unique name such as produced by the
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:885:function `${min_update_index}-${max_update_index}.ref`.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-886-
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-889-
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:890:The stack ordering file is `$GIT_DIR/reftable/tables.list` and lists the
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-891-current files, one per line, in order, from oldest (base) to newest
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-900-
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:901:Readers must read `$GIT_DIR/reftable/tables.list` to determine which
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-902-files are relevant right now, and search through the stack in reverse
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-942-4. Prepare temp reftable `tmp_XXXXXX`, including log entries.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:943:5. Rename `tmp_XXXXXX` to `${update_index}-${update_index}.ref`.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-944-6. Copy `tables.list` to `tables.list.lock`, appending file from (5).
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-989-4. Compact `B` and `C` into a temp file
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:990:`${min_update_index}-${max_update_index}_XXXXXX`.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-991-5. Reacquire lock `tables.list.lock`.
##############################################
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-994-the locking protocol.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:995:7. Rename `${min_update_index}-${max_update_index}_XXXXXX` to
git-2.29.2+next.20201030/Documentation/technical/reftable.txt:996:`${min_update_index}-${max_update_index}.ref`.
git-2.29.2+next.20201030/Documentation/technical/reftable.txt-997-8. Write the new stack to `tables.list.lock`, replacing `B` and `C`
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-8-
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:9:* a remote in the Git configuration file: `$GIT_DIR/config`,
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:10:* a file in the `$GIT_DIR/remotes` directory, or
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:11:* a file in the `$GIT_DIR/branches` directory.
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-12-
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-20-configured using linkgit:git-remote[1], linkgit:git-config[1]
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:21:or even by a manual edit to the `$GIT_DIR/config` file. The URL of
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-22-this remote will be used to access the repository. The refspec
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-37-
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:38:Named file in `$GIT_DIR/remotes`
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-39-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-41-You can choose to provide the name of a
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:42:file in `$GIT_DIR/remotes`. The URL
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-43-in this file will be used to access the repository. The refspec
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-59-
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:60:Named file in `$GIT_DIR/branches`
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-61-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-63-You can choose to provide the name of a
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:64:file in `$GIT_DIR/branches`.
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-65-The URL in this file will be used to access the repository.
##############################################
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-76-refspecs, if you don't provide one on the command line.
git-2.29.2+next.20201030/Documentation/urls-remotes.txt:77:`<branch>` is the name of this file in `$GIT_DIR/branches` and
git-2.29.2+next.20201030/Documentation/urls-remotes.txt-78-`<head>` defaults to `master`.
##############################################
git-2.29.2+next.20201030/Documentation/user-manual.txt-2370- do
git-2.29.2+next.20201030/Documentation/user-manual.txt:2371: if [ `git rev-list $ref..$branch | wc -c` -gt 0 ]
git-2.29.2+next.20201030/Documentation/user-manual.txt-2372- then
##############################################
git-2.29.2+next.20201030/Documentation/user-manual.txt-3999-filename. The 'stage number' is Git's way to say which tree it
git-2.29.2+next.20201030/Documentation/user-manual.txt:4000:came from: stage 1 corresponds to the `$orig` tree, stage 2 to
git-2.29.2+next.20201030/Documentation/user-manual.txt:4001:the `HEAD` tree, and stage 3 to the `$target` tree.
git-2.29.2+next.20201030/Documentation/user-manual.txt-4002-
##############################################
git-2.29.2+next.20201030/Documentation/user-manual.txt-4004-`git read-tree -m`. For example, if the file did not change
git-2.29.2+next.20201030/Documentation/user-manual.txt:4005:from `$orig` to `HEAD` or `$target`, or if the file changed
git-2.29.2+next.20201030/Documentation/user-manual.txt:4006:from `$orig` to `HEAD` and `$orig` to `$target` the same way,
git-2.29.2+next.20201030/Documentation/user-manual.txt-4007-obviously the final outcome is what is in `HEAD`. What the
git-2.29.2+next.20201030/Documentation/user-manual.txt-4008-above example shows is that file `hello.c` was changed from
git-2.29.2+next.20201030/Documentation/user-manual.txt:4009:`$orig` to `HEAD` and `$orig` to `$target` in a different way.
git-2.29.2+next.20201030/Documentation/user-manual.txt-4010-You could resolve this by running your favorite 3-way merge
##############################################
git-2.29.2+next.20201030/Makefile-2223- @FLAGS='$(SCRIPT_DEFINES)'; \
git-2.29.2+next.20201030/Makefile:2224: if test x"$$FLAGS" != x"`cat $@ 2>/dev/null`" ; then \
git-2.29.2+next.20201030/Makefile-2225- echo >&2 " * new script parameters"; \
##############################################
git-2.29.2+next.20201030/Makefile-2287- @FLAGS='$(PERL_DEFINES)'; \
git-2.29.2+next.20201030/Makefile:2288: if test x"$$FLAGS" != x"`cat $@ 2>/dev/null`" ; then \
git-2.29.2+next.20201030/Makefile-2289- echo >&2 " * new perl-specific parameters"; \
##############################################
git-2.29.2+next.20201030/Makefile-2781- @VARS='$(TRACK_PYTHON)'; \
git-2.29.2+next.20201030/Makefile:2782: if test x"$$VARS" != x"`cat $@ 2>/dev/null`" ; then \
git-2.29.2+next.20201030/Makefile-2783- echo >&2 " * new Python interpreter location"; \
##############################################
git-2.29.2+next.20201030/block-sha1/sha1.c-48- * Ben Herrenschmidt reports that on PPC, the C version comes close
git-2.29.2+next.20201030/block-sha1/sha1.c:49: * to the optimized asm with this (ie on PPC you don't want that
git-2.29.2+next.20201030/block-sha1/sha1.c-50- * 'volatile', since there are lots of registers).
##############################################
git-2.29.2+next.20201030/builtin/pull.c-140- PARSE_OPT_NOARG | PARSE_OPT_HIDDEN),
git-2.29.2+next.20201030/builtin/pull.c:141: OPT_PASSTHRU(0, "log", &opt_log, N_("n"),
git-2.29.2+next.20201030/builtin/pull.c-142- N_("add (at most <n>) entries from shortlog to merge commit message"),
##############################################
git-2.29.2+next.20201030/builtin/pull.c-174- 0),
git-2.29.2+next.20201030/builtin/pull.c:175: OPT_PASSTHRU('S', "gpg-sign", &opt_gpg_sign, N_("key-id"),
git-2.29.2+next.20201030/builtin/pull.c-176- N_("GPG sign commit"),
##############################################
git-2.29.2+next.20201030/builtin/pull.c-189- PARSE_OPT_NOARG),
git-2.29.2+next.20201030/builtin/pull.c:190: OPT_PASSTHRU(0, "upload-pack", &opt_upload_pack, N_("path"),
git-2.29.2+next.20201030/builtin/pull.c-191- N_("path to upload pack on remote end"),
##############################################
git-2.29.2+next.20201030/builtin/pull.c-199- PARSE_OPT_NOARG),
git-2.29.2+next.20201030/builtin/pull.c:200: OPT_PASSTHRU('j', "jobs", &max_children, N_("n"),
git-2.29.2+next.20201030/builtin/pull.c-201- N_("number of submodules pulled in parallel"),
##############################################
git-2.29.2+next.20201030/builtin/pull.c-207- PARSE_OPT_NOARG),
git-2.29.2+next.20201030/builtin/pull.c:208: OPT_PASSTHRU(0, "depth", &opt_depth, N_("depth"),
git-2.29.2+next.20201030/builtin/pull.c-209- N_("deepen history of shallow clone"),
##############################################
git-2.29.2+next.20201030/builtin/pull.c-225- PARSE_OPT_NOARG),
git-2.29.2+next.20201030/builtin/pull.c:226: OPT_PASSTHRU(0, "refmap", &opt_refmap, N_("refmap"),
git-2.29.2+next.20201030/builtin/pull.c-227- N_("specify fetch refmap"),
##############################################
git-2.29.2+next.20201030/compat/mingw.c-985- size_t ret;
git-2.29.2+next.20201030/compat/mingw.c:986: DECLARE_PROC_ADDR(ucrtbase.dll, size_t, strftime, char *, size_t,
git-2.29.2+next.20201030/compat/mingw.c-987- const char *, const struct tm *);
git-2.29.2+next.20201030/compat/mingw.c-988-
git-2.29.2+next.20201030/compat/mingw.c:989: if (INIT_PROC_ADDR(strftime))
git-2.29.2+next.20201030/compat/mingw.c-990- ret = strftime(s, max, format, tm);
##############################################
git-2.29.2+next.20201030/compat/mingw.c-2160-{
git-2.29.2+next.20201030/compat/mingw.c:2161: DECLARE_PROC_ADDR(secur32.dll, BOOL, GetUserNameExW,
git-2.29.2+next.20201030/compat/mingw.c-2162- enum EXTENDED_NAME_FORMAT, LPCWSTR, PULONG);
##############################################
git-2.29.2+next.20201030/compat/mingw.c-2165-
git-2.29.2+next.20201030/compat/mingw.c:2166: if (!INIT_PROC_ADDR(GetUserNameExW))
git-2.29.2+next.20201030/compat/mingw.c-2167- return NULL;
##############################################
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-367- supplied C version. Also, the case of x86 using gcc is special-cased
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h:368: to an asm instruction, so is already as fast as it can be, and so
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-369- this setting has no effect. Similarly for Win32 under recent MS compilers.
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h:370: (On most x86s, the asm version is only slightly faster than the C version.)
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-371-
##############################################
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-2754-
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h:2755:/* assign tree index for size S to variable I. Use x86 asm if possible */
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-2756-#if defined(__GNUC__) && (defined(__i386__) || defined(__x86_64__))
##############################################
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-2857-
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h:2858:/* index corresponding to given bit. Use x86 asm if possible */
git-2.29.2+next.20201030/compat/nedmalloc/malloc.c.h-2859-
##############################################
git-2.29.2+next.20201030/compat/win32/lazyload.h-6- *
git-2.29.2+next.20201030/compat/win32/lazyload.h:7: * DECLARE_PROC_ADDR(kernel32.dll, BOOL, CreateHardLinkW,
git-2.29.2+next.20201030/compat/win32/lazyload.h-8- * LPCWSTR, LPCWSTR, LPSECURITY_ATTRIBUTES);
git-2.29.2+next.20201030/compat/win32/lazyload.h-9- *
git-2.29.2+next.20201030/compat/win32/lazyload.h:10: * if (!INIT_PROC_ADDR(CreateHardLinkW))
git-2.29.2+next.20201030/compat/win32/lazyload.h-11- * return error("Could not find CreateHardLinkW() function";
##############################################
git-2.29.2+next.20201030/compat/win32/lazyload.h-25-/* Declares a function to be loaded dynamically from a DLL. */
git-2.29.2+next.20201030/compat/win32/lazyload.h:26:#define DECLARE_PROC_ADDR(dll, rettype, function, ...) \
git-2.29.2+next.20201030/compat/win32/lazyload.h-27- static struct proc_addr proc_addr_##function = \
##############################################
git-2.29.2+next.20201030/compat/win32/lazyload.h-36- */
git-2.29.2+next.20201030/compat/win32/lazyload.h:37:#define INIT_PROC_ADDR(function) \
git-2.29.2+next.20201030/compat/win32/lazyload.h:38: (function = get_proc_addr(&proc_addr_##function))
git-2.29.2+next.20201030/compat/win32/lazyload.h-39-
git-2.29.2+next.20201030/compat/win32/lazyload.h:40:static inline void *get_proc_addr(struct proc_addr *proc)
git-2.29.2+next.20201030/compat/win32/lazyload.h-41-{
##############################################
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c-145-{
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c:146: DECLARE_PROC_ADDR(psapi.dll, BOOL, GetProcessMemoryInfo, HANDLE,
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c-147- PPROCESS_MEMORY_COUNTERS, DWORD);
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c-148-
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c:149: if (INIT_PROC_ADDR(GetProcessMemoryInfo)) {
git-2.29.2+next.20201030/compat/win32/trace2_win32_process_info.c-150- PROCESS_MEMORY_COUNTERS pmc;
##############################################
git-2.29.2+next.20201030/compat/winansi.c-47- DWORD fontFamily = 0;
git-2.29.2+next.20201030/compat/winansi.c:48: DECLARE_PROC_ADDR(kernel32.dll, BOOL, GetCurrentConsoleFontEx,
git-2.29.2+next.20201030/compat/winansi.c-49- HANDLE, BOOL, PCONSOLE_FONT_INFOEX);
##############################################
git-2.29.2+next.20201030/compat/winansi.c-55- /* GetCurrentConsoleFontEx is available since Vista */
git-2.29.2+next.20201030/compat/winansi.c:56: if (INIT_PROC_ADDR(GetCurrentConsoleFontEx)) {
git-2.29.2+next.20201030/compat/winansi.c-57- CONSOLE_FONT_INFOEX cfi;
##############################################
git-2.29.2+next.20201030/config.mak.uname-123- endif
git-2.29.2+next.20201030/config.mak.uname:124: ifeq ($(shell test "`expr "$(uname_R)" : '\([0-9][0-9]*\)\.'`" -ge 11 && echo 1),1)
git-2.29.2+next.20201030/config.mak.uname-125- HAVE_GETDELIM = YesPlease
##############################################
git-2.29.2+next.20201030/config.mak.uname-781- git commit -m "Generate Visual Studio solution" \
git-2.29.2+next.20201030/config.mak.uname:782: -m "Auto-generated by \`$(MAKE)$(MAKEFLAGS) $@\`"
##############################################
git-2.29.2+next.20201030/configure.ac-517- AC_MSG_CHECKING([for asciidoc version])
git-2.29.2+next.20201030/configure.ac:518: asciidoc_version=`$ASCIIDOC --version 2>/dev/null`
git-2.29.2+next.20201030/configure.ac-519- case "${asciidoc_version}" in
##############################################
git-2.29.2+next.20201030/contrib/buildsystems/Generators.pm-37- my ($gen, $git_dir, $out_dir, $rel_dir, %build_structure) = @_;
git-2.29.2+next.20201030/contrib/buildsystems/Generators.pm:38: return eval("Generators::${gen}::generate(\$git_dir, \$out_dir, \$rel_dir, \%build_structure)") if grep(/^$gen$/, @AVAILABLE);
git-2.29.2+next.20201030/contrib/buildsystems/Generators.pm-39- die "Generator \"${gen}\" is not available!\nAvailable generators are: @AVAILABLE\n";
##############################################
git-2.29.2+next.20201030/contrib/buildsystems/engine.pl-84-my $ErrsFile = "msvc-build-makedryerrors.txt";
git-2.29.2+next.20201030/contrib/buildsystems/engine.pl:85:@makedry = `make -C $git_dir -n MSVC=1 SKIP_VCPKG=1 V=1 2>$ErrsFile`
git-2.29.2+next.20201030/contrib/buildsystems/engine.pl-86-if !@makedry;
##############################################
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh-25-
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh:26:set __git_tcsh_completion_version = `\echo ${tcsh} | \sed 's/\./ /g'`
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh-27-if ( ${__git_tcsh_completion_version[1]} < 6 || \
##############################################
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh-105- # Use ls so as to add the '/' at the end of directories.
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh:106: COMPREPLY=(\`ls -dp \${TO_COMPLETE}* 2> /dev/null\`)
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh-107- fi
##############################################
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh-124-
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh:125:complete git 'p,*,`bash ${__git_tcsh_completion_script} git "${COMMAND_LINE}"`,'
git-2.29.2+next.20201030/contrib/completion/git-completion.tcsh:126:complete gitk 'p,*,`bash ${__git_tcsh_completion_script} gitk "${COMMAND_LINE}"`,'
##############################################
git-2.29.2+next.20201030/contrib/diff-highlight/DiffHighlight.pm-141- my ($key, $default) = @_;
git-2.29.2+next.20201030/contrib/diff-highlight/DiffHighlight.pm:142: my $s = `git config --get-color $key 2>$NULL`;
git-2.29.2+next.20201030/contrib/diff-highlight/DiffHighlight.pm-143- return length($s) ? $s : $default;
##############################################
git-2.29.2+next.20201030/contrib/fast-import/import-directories.perl-153-{
git-2.29.2+next.20201030/contrib/fast-import/import-directories.perl:154: exec('perldoc', $0);
git-2.29.2+next.20201030/contrib/fast-import/import-directories.perl-155- exit 1;
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/README.rst-433-
git-2.29.2+next.20201030/contrib/hooks/multimail/README.rst:434: git-multimail will then look for a line where ``$GL_USER``
git-2.29.2+next.20201030/contrib/hooks/multimail/README.rst-435- matches the ``username`` part, and use the rest of the line for
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-19-
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst:20:Create a directory ``$site_path/hooks/`` if it does not exist (if you
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst:21:don't know what ``$site_path`` is, run ``gerrit.sh status`` and look
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-22-for a ``GERRIT_SITE`` line). Either copy ``git_multimail.py`` to
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst:23:``$site_path/hooks/ref-updated`` or create a wrapper script like
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-24-this::
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-29-In both cases, make sure the file is named exactly
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst:30:``$site_path/hooks/ref-updated`` and is executable.
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-31-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-37-
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst:38:Log on the gerrit server and edit ``$site_path/git/$project/config``
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/gerrit.rst-39-to configure ``git-multimail``.
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/troubleshooting.rst-34-
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/troubleshooting.rst:35:Do not set ``$GIT_MULTIMAIL_CHECK_SETUP`` other than for testing your
git-2.29.2+next.20201030/contrib/hooks/multimail/doc/troubleshooting.rst-36-configuration: it would disable the hook completely.
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-554- text = ', '.join(
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:555: formataddr((header_encode(name), emailaddr))
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-556- for name, emailaddr in getaddresses([text])
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-690- for pair in getaddresses([value]):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:691: self.add(name, formataddr(pair))
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-692-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-822- values = self.environment.get_values()
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:823: fromaddr = self.environment.get_fromaddr(change=self)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-824- if fromaddr is not None:
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1057-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:1058: def get_specific_fromaddr(self):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1059- """For kinds of Changes which specify it, return the kind-specific
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1184-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:1185: def get_specific_fromaddr(self):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1186- return self.environment.from_commit
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1649-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:1650: def get_specific_fromaddr(self):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-1651- return self.environment.from_refchange
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2303-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2304: get_fromaddr(change=None)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2305-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2489-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2490: def get_fromaddr(self, change=None):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2491- config = Config('user')
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2494- if fromemail:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2495: return formataddr([fromname, fromemail])
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2496- return self.get_sender()
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2781-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2782: def process_addr(self, addr, change):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2783- if addr.lower() == 'author':
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2794-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2795: def get_fromaddr(self, change=None):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2796- fromaddr = self.config.get('from')
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2797- if change:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2798: specific_fromaddr = change.get_specific_fromaddr()
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2799- if specific_fromaddr:
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2801- if fromaddr:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2802: fromaddr = self.process_addr(fromaddr, change)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2803- if fromaddr:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2804- return fromaddr
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2805: return super(ConfigOptionsEnvironmentMixin, self).get_fromaddr(change)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2806-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2810- else:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2811: return self.process_addr(self.__reply_to_refchange, refchange)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2812-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2816- else:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:2817: return self.process_addr(self.__reply_to_commit, revision)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-2818-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3237-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3238: def get_fromaddr(self, change=None):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3239- GL_USER = self.osenv.get('GL_USER')
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3298- f.close()
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3299: return super(GitoliteEnvironmentLowPrecMixin, self).get_fromaddr(change)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3300-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3342-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3343: def get_fromaddr(self, change=None):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3344- return self.__user
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3409-
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3410: def get_fromaddr(self, change=None):
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3411- if self.__submitter and self.__submitter.find('<') != -1:
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3413- else:
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3414: return super(GerritEnvironmentLowPrecMixin, self).get_fromaddr(change)
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3415-
##############################################
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3884- environment,
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py:3885: envelopesender=(environment.get_sender() or environment.get_fromaddr()),
git-2.29.2+next.20201030/contrib/hooks/multimail/git_multimail.py-3886- smtpserver=smtpserver, smtpservertimeout=smtpservertimeout,
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-97- if (-e "$gitdir/MERGE_MSG") {
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:98: if (`grep ====== $gitmeta`) {
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-99- # Conflict not resolved -- abort the commit
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-104- }
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:105: elsif (`grep $gitmeta $gitdir/MERGE_MSG`) {
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-106- # A conflict in .gitmeta has been manually resolved. Verify that
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-111- # may not be consistent with the manually merged .gitmeta file.
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:112: my @conflict_diff = `git show \$(cat $gitdir/MERGE_HEAD)`;
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-113- my @conflict_files;
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-132- my $absfile = $topdir . $file;
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:133: my $gm_entry = `grep "^$file mode=" $gitmeta`;
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-134- if ($gm_entry =~ /mode=(\d+) uid=(\d+) gid=(\d+)/) {
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-182- else {
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:183: my $diff = `diff -U 0 $gitmeta $gitmeta.tmp`;
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-184- if ($diff ne '') {
##############################################
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-196- # Make sure the .gitmeta file is tracked
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl:197: system("git add $gitmeta");
git-2.29.2+next.20201030/contrib/hooks/setgitperms.perl-198-}
##############################################
git-2.29.2+next.20201030/contrib/mw-to-git/git-mw.perl-213- v_print("Launching browser w/ file: ${preview_file_name}");
git-2.29.2+next.20201030/contrib/mw-to-git/git-mw.perl:214: system('git', 'web--browse', $preview_file_name);
git-2.29.2+next.20201030/contrib/mw-to-git/git-mw.perl-215- } else {
##############################################
git-2.29.2+next.20201030/contrib/persistent-https/client.go-97-
git-2.29.2+next.20201030/contrib/persistent-https/client.go:98: if addr, err = c.readAddr(uconn); err != nil {
git-2.29.2+next.20201030/contrib/persistent-https/client.go-99- return
##############################################
git-2.29.2+next.20201030/contrib/persistent-https/client.go-108- var addr2 string
git-2.29.2+next.20201030/contrib/persistent-https/client.go:109: if addr2, err = c.readAddr(uconn); err != nil {
git-2.29.2+next.20201030/contrib/persistent-https/client.go-110- return
##############################################
git-2.29.2+next.20201030/contrib/persistent-https/client.go-117-
git-2.29.2+next.20201030/contrib/persistent-https/client.go:118:func (c *Client) readAddr(conn net.Conn) (string, error) {
git-2.29.2+next.20201030/contrib/persistent-https/client.go-119- conn.SetDeadline(time.Now().Add(5 * time.Second))
##############################################
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go-73-
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go:74: p.httpAddr = hl.Addr().String()
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go:75: p.httpsAddr = hsl.Addr().String()
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go-76- fmt.Printf("OK\nListening on unix socket=%v http=%v https=%v\n",
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go:77: p.ul.Addr(), p.httpAddr, p.httpsAddr)
git-2.29.2+next.20201030/contrib/persistent-https/proxy.go-78-
##############################################
git-2.29.2+next.20201030/contrib/subtree/t/Makefile-58-test-lint-duplicates:
git-2.29.2+next.20201030/contrib/subtree/t/Makefile:59: @dups=`echo $(T) | tr ' ' '\n' | sed 's/-.*//' | sort | uniq -d` && \
git-2.29.2+next.20201030/contrib/subtree/t/Makefile-60- test -z "$$dups" || { \
##############################################
git-2.29.2+next.20201030/contrib/subtree/t/Makefile-63-test-lint-executable:
git-2.29.2+next.20201030/contrib/subtree/t/Makefile:64: @bad=`for i in $(T); do test -x "$$i" || echo $$i; done` && \
git-2.29.2+next.20201030/contrib/subtree/t/Makefile-65- test -z "$$bad" || { \
##############################################
git-2.29.2+next.20201030/contrib/vscode/init.sh-369- git --no-pager diff --no-index $file $file.new
git-2.29.2+next.20201030/contrib/vscode/init.sh:370: printf "\n\nMaybe \`mv $file.new $file\`?\n\n"
git-2.29.2+next.20201030/contrib/vscode/init.sh-371- fi
##############################################
git-2.29.2+next.20201030/daemon.c-949-
git-2.29.2+next.20201030/daemon.c:950:static int set_reuse_addr(int sockfd)
git-2.29.2+next.20201030/daemon.c-951-{
##############################################
git-2.29.2+next.20201030/daemon.c-1032-
git-2.29.2+next.20201030/daemon.c:1033: if (set_reuse_addr(sockfd)) {
git-2.29.2+next.20201030/daemon.c-1034- logerror("Could not set SO_REUSEADDR: %s", strerror(errno));
##############################################
git-2.29.2+next.20201030/daemon.c-1093-
git-2.29.2+next.20201030/daemon.c:1094: if (set_reuse_addr(sockfd)) {
git-2.29.2+next.20201030/daemon.c-1095- logerror("Could not set SO_REUSEADDR: %s", strerror(errno));
##############################################
git-2.29.2+next.20201030/git-add--interactive.perl-1137- chomp(my ($editor) = run_cmd_pipe(qw(git var GIT_EDITOR)));
git-2.29.2+next.20201030/git-add--interactive.perl:1138: system('sh', '-c', $editor.' "$@"', $editor, $hunkfile);
git-2.29.2+next.20201030/git-add--interactive.perl-1139-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-345- if (-e "$git_dir/refs/heads/$ps->{branch}") {
git-2.29.2+next.20201030/git-archimport.perl:346: system('git-checkout','-f',$ps->{branch}) == 0 or die "$! $?\n";
git-2.29.2+next.20201030/git-archimport.perl-347-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-369- if (! -e "$git_dir/refs/heads/$ps->{branch}") {
git-2.29.2+next.20201030/git-archimport.perl:370: system('git-branch',$ps->{branch},$branchpoint) == 0 or die "$! $?\n";
git-2.29.2+next.20201030/git-archimport.perl-371-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-380- }
git-2.29.2+next.20201030/git-archimport.perl:381: system('git-checkout','-f',$ps->{branch}) == 0 or die "$! $?\n";
git-2.29.2+next.20201030/git-archimport.perl-382-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-415- # we know about this branch
git-2.29.2+next.20201030/git-archimport.perl:416: system('git-checkout',$ps->{branch});
git-2.29.2+next.20201030/git-archimport.perl-417- } else {
##############################################
git-2.29.2+next.20201030/git-archimport.perl-425- if (! -e "$git_dir/refs/heads/$ps->{branch}") {
git-2.29.2+next.20201030/git-archimport.perl:426: system('git-branch',$ps->{branch},$branchpoint) == 0 or die "$! $?\n";
git-2.29.2+next.20201030/git-archimport.perl-427-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-436- }
git-2.29.2+next.20201030/git-archimport.perl:437: system('git-checkout',$ps->{branch}) == 0 or die "$! $?\n";
git-2.29.2+next.20201030/git-archimport.perl-438- return 0;
##############################################
git-2.29.2+next.20201030/git-archimport.perl-498- rename($from, $to) or die "Error renaming '$from' '$to': $!\n";
git-2.29.2+next.20201030/git-archimport.perl:499: system('git-update-index','--remove','--',$from) == 0 or
git-2.29.2+next.20201030/git-archimport.perl-500- die "Error in git-update-index --remove: $! $?\n";
git-2.29.2+next.20201030/git-archimport.perl:501: system('git-update-index','--add','--',$to) == 0 or
git-2.29.2+next.20201030/git-archimport.perl-502- die "Error in git-update-index --add: $! $?\n";
##############################################
git-2.29.2+next.20201030/git-archimport.perl-622- close HEAD;
git-2.29.2+next.20201030/git-archimport.perl:623: system('git-update-ref', 'HEAD', "$ps->{branch}");
git-2.29.2+next.20201030/git-archimport.perl-624-
##############################################
git-2.29.2+next.20201030/git-archimport.perl-721- # apply patches
git-2.29.2+next.20201030/git-archimport.perl:722: if (`find $tmp/changeset/patches -type f -name '*.patch'`) {
git-2.29.2+next.20201030/git-archimport.perl-723- # this can be sped up considerably by doing
##############################################
git-2.29.2+next.20201030/git-archimport.perl-729- # slow and safe, we invoke patch once per patchfile
git-2.29.2+next.20201030/git-archimport.perl:730: `find $tmp/changeset/patches -type f -name '*.patch' -print0 | grep -zv '{arch}' | xargs -iFILE -0 --no-run-if-empty patch -p1 --forward -iFILE`;
git-2.29.2+next.20201030/git-archimport.perl-731- die "Problem applying patches! $!" if $?;
##############################################
git-2.29.2+next.20201030/git-archimport.perl-734- # apply changed binary files
git-2.29.2+next.20201030/git-archimport.perl:735: if (my @modified = `find $tmp/changeset/patches -type f -name '*.modified'`) {
git-2.29.2+next.20201030/git-archimport.perl-736- foreach my $mod (@modified) {
##############################################
git-2.29.2+next.20201030/git-archimport.perl-741- #print "rsync -p '$mod' '$orig'";
git-2.29.2+next.20201030/git-archimport.perl:742: system('rsync','-p',$mod,"./$orig");
git-2.29.2+next.20201030/git-archimport.perl-743- die "Problem applying binary changes! $!" if $?;
##############################################
git-2.29.2+next.20201030/git-archimport.perl-997- my $branchtip = git_rev_parse($ps->{branch});
git-2.29.2+next.20201030/git-archimport.perl:998: my @ancestors = `git-rev-list --topo-order $branchtip ^$mergebase`;
git-2.29.2+next.20201030/git-archimport.perl-999- my %have; # collected merges this branch has
##############################################
git-2.29.2+next.20201030/git-archimport.perl-1020- my $otherbranchtip = git_rev_parse($branch);
git-2.29.2+next.20201030/git-archimport.perl:1021: my @needraw = `git-rev-list --topo-order $otherbranchtip ^$mergebase`;
git-2.29.2+next.20201030/git-archimport.perl-1022- my @need;
##############################################
git-2.29.2+next.20201030/git-archimport.perl-1103- } else {
git-2.29.2+next.20201030/git-archimport.perl:1104: exec(@_) or die "$! $?"; # exec() can fail the executable can't be found
git-2.29.2+next.20201030/git-archimport.perl-1105- }
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-144- git rev-parse HEAD` || die "Could not determine current branch";
git-2.29.2+next.20201030/git-cvsexportcommit.perl:145: system("git checkout -q $parent^0") && die "Could not check out $parent^0";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-146-}
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-164-if ($parent eq $noparent) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:165: `git diff-tree --binary -p --root $commit >.cvsexportcommit.diff`;# || die "Cannot diff";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-166-} else {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:167: `git diff-tree --binary -p $parent $commit >.cvsexportcommit.diff`;# || die "Cannot diff";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-168-}
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-333-if ($opt_W) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:334: system("git checkout -q $commit^0") && die "cannot patch";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-335-} else {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:336: `GIT_INDEX_FILE=$tmpdir/index git apply $context --summary --numstat --apply <.cvsexportcommit.diff` || die "cannot patch";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-337-}
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-352-foreach my $d (@dirs) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:353: if (system(@cvs,'add',$d)) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl-354- $dirtypatch = 1;
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-360- if (grep { $_ eq $f } @bfiles) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:361: system(@cvs, 'add','-kb',$f);
git-2.29.2+next.20201030/git-cvsexportcommit.perl-362- } else {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:363: system(@cvs, 'add', $f);
git-2.29.2+next.20201030/git-cvsexportcommit.perl-364- }
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-371-foreach my $f (@dfiles) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:372: system(@cvs, 'rm', '-f', $f);
git-2.29.2+next.20201030/git-cvsexportcommit.perl-373- if ($?) {
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-412-if ($opt_W) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:413: system("git checkout $go_back_to") && die "cannot move back to $go_back_to";
git-2.29.2+next.20201030/git-cvsexportcommit.perl-414- if (!($go_back_to =~ /^[0-9a-fA-F]{$hexsz}$/)) {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:415: system("git symbolic-ref HEAD $go_back_to") &&
git-2.29.2+next.20201030/git-cvsexportcommit.perl-416- die "cannot move back to $go_back_to";
##############################################
git-2.29.2+next.20201030/git-cvsexportcommit.perl-441- } else {
git-2.29.2+next.20201030/git-cvsexportcommit.perl:442: exec(@_) or die "$! $?"; # exec() can fail the executable can't be found
git-2.29.2+next.20201030/git-cvsexportcommit.perl-443- }
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-139- }
git-2.29.2+next.20201030/git-cvsimport.perl:140: chomp(my $tmp = `$arg --get cvsimport.$ckey`);
git-2.29.2+next.20201030/git-cvsimport.perl-141- if ($tmp && !($arg =~ /--bool/ && $tmp eq 'false')) {
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-647- $name =~ s/'/'\\''/g;
git-2.29.2+next.20201030/git-cvsimport.perl:648: my $r = `git rev-parse --verify '$name' 2>/dev/null`;
git-2.29.2+next.20201030/git-cvsimport.perl-649- return undef unless $? == 0;
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-709- my ($ref, $author);
git-2.29.2+next.20201030/git-cvsimport.perl:710: eval($entry) || die "cannot eval refs list: $@";
git-2.29.2+next.20201030/git-cvsimport.perl-711- my ($head) = ($ref =~ m|^$remote/(.*)|);
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-757- }
git-2.29.2+next.20201030/git-cvsimport.perl:758: exec("cvsps","--norc",@opt,"-u","-A",'--root',$opt_d,$cvs_tree);
git-2.29.2+next.20201030/git-cvsimport.perl-759- die "Could not start cvsps: $!\n";
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-840- if ($ancestor) {
git-2.29.2+next.20201030/git-cvsimport.perl:841: system("git", "read-tree", "$remote/$ancestor");
git-2.29.2+next.20201030/git-cvsimport.perl-842- } else {
git-2.29.2+next.20201030/git-cvsimport.perl:843: system("git", "read-tree", "$remote/$branch");
git-2.29.2+next.20201030/git-cvsimport.perl-844- }
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-905-
git-2.29.2+next.20201030/git-cvsimport.perl:906: system('git' , 'update-ref', "$remote/$branch", $cid) == 0
git-2.29.2+next.20201030/git-cvsimport.perl-907- or die "Cannot write branch $branch for update: $!\n";
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-939-
git-2.29.2+next.20201030/git-cvsimport.perl:940: if (system('git' , 'tag', '-f', $xtag, $cid) != 0) {
git-2.29.2+next.20201030/git-cvsimport.perl-941- # We did our best to sanitize the tag, but still failed
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-1087- if (!$pid) {
git-2.29.2+next.20201030/git-cvsimport.perl:1088: exec("git", "hash-object", "-w", $tmpname)
git-2.29.2+next.20201030/git-cvsimport.perl-1089- or die "Cannot create object: $!\n";
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-1167- else {
git-2.29.2+next.20201030/git-cvsimport.perl:1168: system(qw(git merge -m cvsimport), "$remote/$opt_o");
git-2.29.2+next.20201030/git-cvsimport.perl-1169- die "Could not merge $opt_o into the current branch.\n" if $?;
##############################################
git-2.29.2+next.20201030/git-cvsimport.perl-1173- print "DONE; creating $orig_branch branch\n" if $opt_v;
git-2.29.2+next.20201030/git-cvsimport.perl:1174: system("git", "update-ref", "refs/heads/master", "$remote/$opt_o")
git-2.29.2+next.20201030/git-cvsimport.perl-1175- unless defined get_headref('refs/heads/master');
git-2.29.2+next.20201030/git-cvsimport.perl:1176: system("git", "symbolic-ref", "$remote/HEAD", "$remote/$opt_o")
git-2.29.2+next.20201030/git-cvsimport.perl-1177- if ($opt_r && $opt_o ne 'HEAD');
git-2.29.2+next.20201030/git-cvsimport.perl:1178: system('git', 'update-ref', 'HEAD', "$orig_branch");
git-2.29.2+next.20201030/git-cvsimport.perl-1179- unless ($opt_i) {
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1397- my $mergedFile = "$mergeDir/$file_local";
git-2.29.2+next.20201030/git-cvsserver.perl:1398: system("ln","-s",$state->{entries}{$filename}{modified_filename}, $file_local);
git-2.29.2+next.20201030/git-cvsserver.perl-1399- my $file_old = $filepart . "." . $oldmeta->{revision};
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1409-
git-2.29.2+next.20201030/git-cvsserver.perl:1410: my $return = system("git", "merge-file", $file_local, $file_old, $file_new);
git-2.29.2+next.20201030/git-cvsserver.perl-1411- $return >>= 8;
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1590- {
git-2.29.2+next.20201030/git-cvsserver.perl:1591: print "error 1 sticky tag `$stickyInfo->{tag}' for file `$filename' is not a branch\n";
git-2.29.2+next.20201030/git-cvsserver.perl-1592- }
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1629- if ($wrev) {
git-2.29.2+next.20201030/git-cvsserver.perl:1630: system('git', 'checkout-index', '-f', '-u', $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-1631- unless ($? == 0) {
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1653-
git-2.29.2+next.20201030/git-cvsserver.perl:1654: system("mkdir","-p",$dirpart) unless ( -d $dirpart );
git-2.29.2+next.20201030/git-cvsserver.perl-1655-
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1665- $log->debug("chmod u+" . $state->{entries}{$filename}{modified_mode} . "-" . $invmode . " $filename");
git-2.29.2+next.20201030/git-cvsserver.perl:1666: system("chmod","u+" . $state->{entries}{$filename}{modified_mode} . "-" . $invmode, $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-1667- }
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1672- unlink($filename);
git-2.29.2+next.20201030/git-cvsserver.perl:1673: system("git", "update-index", "--remove", $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-1674- }
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1677- $log->info("Adding file '$filename'");
git-2.29.2+next.20201030/git-cvsserver.perl:1678: system("git", "update-index", "--add", $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-1679- } else {
git-2.29.2+next.20201030/git-cvsserver.perl-1680- $log->info("UpdatingX2 file '$filename'");
git-2.29.2+next.20201030/git-cvsserver.perl:1681: system("git", "update-index", $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-1682- }
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-1760- if (-x $hook) {
git-2.29.2+next.20201030/git-cvsserver.perl:1761: system($hook, $branchRef);
git-2.29.2+next.20201030/git-cvsserver.perl-1762- }
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-2330- # the current head as we do now)
git-2.29.2+next.20201030/git-cvsserver.perl:2331: system("git", "read-tree", $lastseenin);
git-2.29.2+next.20201030/git-cvsserver.perl-2332- unless ($? == 0)
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-2339- # do a checkout of the file
git-2.29.2+next.20201030/git-cvsserver.perl:2340: system('git', 'checkout-index', '-f', '-u', $filename);
git-2.29.2+next.20201030/git-cvsserver.perl-2341- unless ($? == 0) {
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-3010- {
git-2.29.2+next.20201030/git-cvsserver.perl:3011: system("git","read-tree",$ver);
git-2.29.2+next.20201030/git-cvsserver.perl-3012- unless ($? == 0)
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-3064-
git-2.29.2+next.20201030/git-cvsserver.perl:3065: system("git","read-tree",$ver);
git-2.29.2+next.20201030/git-cvsserver.perl-3066- unless ($? == 0)
##############################################
git-2.29.2+next.20201030/git-cvsserver.perl-3422- } else {
git-2.29.2+next.20201030/git-cvsserver.perl:3423: exec(@_) or die "$! $?"; # exec() can fail the executable can't be found
git-2.29.2+next.20201030/git-cvsserver.perl-3424- }
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-80- INSTALL_R0 = src=
git-2.29.2+next.20201030/git-gui/Makefile:81: INSTALL_R1 = && echo ' ' INSTALL 644 `basename $$src` && $(INSTALL) -m 644 $$src
git-2.29.2+next.20201030/git-gui/Makefile-82- INSTALL_X0 = src=
git-2.29.2+next.20201030/git-gui/Makefile:83: INSTALL_X1 = && echo ' ' INSTALL 755 `basename $$src` && $(INSTALL) -m 755 $$src
git-2.29.2+next.20201030/git-gui/Makefile-84- INSTALL_A0 = src=
git-2.29.2+next.20201030/git-gui/Makefile:85: INSTALL_A1 = && echo ' ' INSTALL ' ' `basename "$$src"` && find "$$src" | cpio -pud
git-2.29.2+next.20201030/git-gui/Makefile-86-
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-89- INSTALL_L2 = && dst=
git-2.29.2+next.20201030/git-gui/Makefile:90: INSTALL_L3 = && echo ' ' 'LINK ' `basename "$$dst"` '->' `basename "$$src"` && rm -f "$$dst" && ln "$$src" "$$dst"
git-2.29.2+next.20201030/git-gui/Makefile-91-
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-95- REMOVE_F0 = dst=
git-2.29.2+next.20201030/git-gui/Makefile:96: REMOVE_F1 = && echo ' ' REMOVE `basename "$$dst"` && $(RM_RF) "$$dst"
git-2.29.2+next.20201030/git-gui/Makefile-97-endif
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-139-ifeq ($(uname_O),Cygwin)
git-2.29.2+next.20201030/git-gui/Makefile:140: GITGUI_SCRIPT := `cygpath --windows --absolute "$(GITGUI_SCRIPT)"`
git-2.29.2+next.20201030/git-gui/Makefile-141-
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-278- @VARS='$(TRACK_VARS)'; \
git-2.29.2+next.20201030/git-gui/Makefile:279: if test x"$$VARS" != x"`cat $@ 2>/dev/null`" ; then \
git-2.29.2+next.20201030/git-gui/Makefile-280- echo >&2 " * new locations or Tcl/Tk interpreter"; \
##############################################
git-2.29.2+next.20201030/git-gui/Makefile-329- $(QUIET)$(REMOVE_D0)'$(DESTDIR_SQ)$(libdir_SQ)' $(REMOVE_D1)
git-2.29.2+next.20201030/git-gui/Makefile:330: $(QUIET)$(REMOVE_D0)`dirname '$(DESTDIR_SQ)$(libdir_SQ)'` $(REMOVE_D1)
git-2.29.2+next.20201030/git-gui/Makefile-331-
##############################################
git-2.29.2+next.20201030/git-gui/git-gui.sh-1227-##
git-2.29.2+next.20201030/git-gui/git-gui.sh:1228:## execution environment
git-2.29.2+next.20201030/git-gui/git-gui.sh-1229-
##############################################
git-2.29.2+next.20201030/git-p4.py-1939- editor = read_pipe("git var GIT_EDITOR").strip()
git-2.29.2+next.20201030/git-p4.py:1940: system(["sh", "-c", ('%s "$@"' % editor), editor, template_file])
git-2.29.2+next.20201030/git-p4.py-1941-
##############################################
git-2.29.2+next.20201030/git-send-email.perl-97- --identity <str> * Use the sendemail.<id> options.
git-2.29.2+next.20201030/git-send-email.perl:98: --to-cmd <str> * Email To: via `<str> \$patch_path`
git-2.29.2+next.20201030/git-send-email.perl:99: --cc-cmd <str> * Email Cc: via `<str> \$patch_path`
git-2.29.2+next.20201030/git-send-email.perl-100- --suppress-cc <str> * author, self, sob, cc, cccmd, body, bodycc, misc-by, all.
##############################################
git-2.29.2+next.20201030/git-send-email.perl-220- map {
git-2.29.2+next.20201030/git-send-email.perl:221: system('sh', '-c', $editor.' "$@"', $editor, $_);
git-2.29.2+next.20201030/git-send-email.perl-222- if (($? & 127) || ($? >> 8)) {
##############################################
git-2.29.2+next.20201030/git-send-email.perl-226- } else {
git-2.29.2+next.20201030/git-send-email.perl:227: system('sh', '-c', $editor.' "$@"', $editor, @_);
git-2.29.2+next.20201030/git-send-email.perl-228- if (($? & 127) || ($? >> 8)) {
##############################################
git-2.29.2+next.20201030/git-send-email.perl-1491- if (!$pid) {
git-2.29.2+next.20201030/git-send-email.perl:1492: exec($smtp_server, @sendmail_parameters) or die $!;
git-2.29.2+next.20201030/git-send-email.perl-1493- }
##############################################
git-2.29.2+next.20201030/git-send-email.perl-1671- elsif (/^To:\s+(.*)$/i) {
git-2.29.2+next.20201030/git-send-email.perl:1672: foreach my $addr (parse_address_line($1)) {
git-2.29.2+next.20201030/git-send-email.perl-1673- printf(__("(mbox) Adding to: %s from line '%s'\n"),
##############################################
git-2.29.2+next.20201030/git-send-email.perl-1678- elsif (/^Cc:\s+(.*)$/i) {
git-2.29.2+next.20201030/git-send-email.perl:1679: foreach my $addr (parse_address_line($1)) {
git-2.29.2+next.20201030/git-send-email.perl-1680- my $qaddr = unquote_rfc2047($addr);
##############################################
git-2.29.2+next.20201030/git-send-email.perl-1955- $hook_error = "rejected by sendemail-validate hook"
git-2.29.2+next.20201030/git-send-email.perl:1956: if system($validate_hook, $target);
git-2.29.2+next.20201030/git-send-email.perl-1957- chdir($cwd_save) or die("chdir: $!");
##############################################
git-2.29.2+next.20201030/git-svn.perl-1395- if (not defined $props->{$prop}) {
git-2.29.2+next.20201030/git-svn.perl:1396: fatal("`$path' does not have a `$prop' SVN property.");
git-2.29.2+next.20201030/git-svn.perl-1397- }
##############################################
git-2.29.2+next.20201030/git-svn.perl-1890- chomp(my $editor = command_oneline(qw(var GIT_EDITOR)));
git-2.29.2+next.20201030/git-svn.perl:1891: system('sh', '-c', $editor.' "$@"', $editor, $commit_editmsg);
git-2.29.2+next.20201030/git-svn.perl-1892- }
##############################################
git-2.29.2+next.20201030/git-svn.perl-1971- if (ref $v eq 'ARRAY') {
git-2.29.2+next.20201030/git-svn.perl:1972: chomp(my @tmp = `$arg --get-all svn.$key`);
git-2.29.2+next.20201030/git-svn.perl-1973- @$v = @tmp if @tmp;
git-2.29.2+next.20201030/git-svn.perl-1974- } else {
git-2.29.2+next.20201030/git-svn.perl:1975: chomp(my $tmp = `$arg --get svn.$key`);
git-2.29.2+next.20201030/git-svn.perl-1976- if ($tmp && !($arg =~ / --bool/ && $tmp eq 'false')) {
##############################################
git-2.29.2+next.20201030/gitk-git/Makefile-24- @VARS='$(TRACK_TCLTK)'; \
git-2.29.2+next.20201030/gitk-git/Makefile:25: if test x"$$VARS" != x"`cat $@ 2>/dev/null`" ; then \
git-2.29.2+next.20201030/gitk-git/Makefile-26- echo 1>&2 " * new Tcl/Tk interpreter location"; \
##############################################
git-2.29.2+next.20201030/gitweb/gitweb.perl-2490- # or we would have to use more complicated regexp, for example
git-2.29.2+next.20201030/gitweb/gitweb.perl:2491: # qr/(?= {0,$m}\+)[+ ]{$num_sign}/, where $m = $num_sign - 1;
git-2.29.2+next.20201030/gitweb/gitweb.perl-2492- { regexp => qr/^[+ ]{$num_sign}/, class => "add" },
##############################################
git-2.29.2+next.20201030/gitweb/gitweb.perl-7656-
git-2.29.2+next.20201030/gitweb/gitweb.perl:7657: system(git_cmd(), "cat-file", '-e', $hash_base) == 0
git-2.29.2+next.20201030/gitweb/gitweb.perl-7658- or die_error(404, "Base object does not exist");
##############################################
git-2.29.2+next.20201030/parse-options-cb.c-262- */
git-2.29.2+next.20201030/parse-options-cb.c:263:int parse_opt_passthru(const struct option *opt, const char *arg, int unset)
git-2.29.2+next.20201030/parse-options-cb.c-264-{
##############################################
git-2.29.2+next.20201030/parse-options.h-302- const char *, int);
git-2.29.2+next.20201030/parse-options.h:303:int parse_opt_passthru(const struct option *, const char *, int);
git-2.29.2+next.20201030/parse-options.h-304-int parse_opt_passthru_argv(const struct option *, const char *, int);
##############################################
git-2.29.2+next.20201030/parse-options.h-322- { OPTION_CALLBACK, (s), (l), (v), N_("style"), (h), PARSE_OPT_OPTARG, parseopt_column_callback }
git-2.29.2+next.20201030/parse-options.h:323:#define OPT_PASSTHRU(s, l, v, a, h, f) \
git-2.29.2+next.20201030/parse-options.h-324- { OPTION_CALLBACK, (s), (l), (v), (a), (h), (f), parse_opt_passthru }
##############################################
git-2.29.2+next.20201030/path.c-1361- * type for directories, allowing `.git/` to be accessed via
git-2.29.2+next.20201030/path.c:1362: * `.git::$INDEX_ALLOCATION/`.
git-2.29.2+next.20201030/path.c-1363- *
##############################################
git-2.29.2+next.20201030/path.c-1368- * For performance reasons, _all_ Alternate Data Streams of `.git/` are
git-2.29.2+next.20201030/path.c:1369: * forbidden, not just `::$INDEX_ALLOCATION`.
git-2.29.2+next.20201030/path.c-1370- *
##############################################
git-2.29.2+next.20201030/perl/Git.pm-483- } elsif ($pid == 0) {
git-2.29.2+next.20201030/perl/Git.pm:484: _cmd_exec($self, $cmd, @args);
git-2.29.2+next.20201030/perl/Git.pm-485- }
##############################################
git-2.29.2+next.20201030/perl/Git.pm-1657- }
git-2.29.2+next.20201030/perl/Git.pm:1658: _cmd_exec($self, $cmd, @args);
git-2.29.2+next.20201030/perl/Git.pm-1659- }
##############################################
git-2.29.2+next.20201030/perl/Git/SVN.pm-1478- $orig_author = command_oneline('rev-parse', '--sq-quote', $orig_author);
git-2.29.2+next.20201030/perl/Git/SVN.pm:1479: my $author = `$::_authors_prog $orig_author`;
git-2.29.2+next.20201030/perl/Git/SVN.pm-1480- if ($? != 0) {
##############################################
git-2.29.2+next.20201030/po/bg.po-163-# grep '^#: ' todo.po | sed 's/^#: //' | tr ' ' '\n' | sed 's/:[0-9]*$//' > FILES
git-2.29.2+next.20201030/po/bg.po:164:# for i in `sort -u FILES`; do cnt=`grep $i FILES | wc -l`; echo $cnt $i ;done | sort -n
git-2.29.2+next.20201030/po/bg.po-165-msgid ""
##############################################
git-2.29.2+next.20201030/t/Makefile-84-test-lint-duplicates:
git-2.29.2+next.20201030/t/Makefile:85: @dups=`echo $(T) $(TPERF) | tr ' ' '\n' | sed 's/-.*//' | sort | uniq -d` && \
git-2.29.2+next.20201030/t/Makefile-86- test -z "$$dups" || { \
##############################################
git-2.29.2+next.20201030/t/Makefile-89-test-lint-executable:
git-2.29.2+next.20201030/t/Makefile:90: @bad=`for i in $(T) $(TPERF); do test -x "$$i" || echo $$i; done` && \
git-2.29.2+next.20201030/t/Makefile-91- test -z "$$bad" || { \
##############################################
git-2.29.2+next.20201030/t/README-231-GIT_EXEC_PATH would be used for during normal operation).
git-2.29.2+next.20201030/t/README:232:GIT_TEST_EXEC_PATH defaults to `$GIT_TEST_INSTALLED/git --exec-path`.
git-2.29.2+next.20201030/t/README-233-
##############################################
git-2.29.2+next.20201030/t/check-non-portable-shell.pl-43- /\btest\s+[^=]*==/ and err '"test a == b" is not portable (use =)';
git-2.29.2+next.20201030/t/check-non-portable-shell.pl:44: /\bwc -l.*"\s*=/ and err '`"$(wc -l)"` is not portable (use test_line_count)';
git-2.29.2+next.20201030/t/check-non-portable-shell.pl-45- /\bhead\s+-c\b/ and err 'head -c is not portable (use test_copy_bytes BYTES <file >out)';
##############################################
git-2.29.2+next.20201030/t/helper/test-drop-caches.c-88- HANDLE hToken;
git-2.29.2+next.20201030/t/helper/test-drop-caches.c:89: DECLARE_PROC_ADDR(ntdll.dll, DWORD, NtSetSystemInformation, INT, PVOID, ULONG);
git-2.29.2+next.20201030/t/helper/test-drop-caches.c-90- SYSTEM_MEMORY_LIST_COMMAND command;
##############################################
git-2.29.2+next.20201030/t/helper/test-drop-caches.c-100-
git-2.29.2+next.20201030/t/helper/test-drop-caches.c:101: if (!INIT_PROC_ADDR(NtSetSystemInformation))
git-2.29.2+next.20201030/t/helper/test-drop-caches.c-102- return error("Could not find NtSetSystemInformation() function");
##############################################
git-2.29.2+next.20201030/t/lib-git-svn.sh-33-\$SVN::Core::VERSION gt '1.1.0' or exit(42);
git-2.29.2+next.20201030/t/lib-git-svn.sh:34:system(qw/svnadmin create --fs-type fsfs/, \$ENV{svnrepo}) == 0 or exit(41);
git-2.29.2+next.20201030/t/lib-git-svn.sh-35-" >&3 2>&4
##############################################
git-2.29.2+next.20201030/t/oid-info/README-4-starting with `#` are ignored. The key and value are separated by whitespace
git-2.29.2+next.20201030/t/oid-info/README:5:(specifically, those whitespace in the default `$IFS`). The key consists only
git-2.29.2+next.20201030/t/oid-info/README-6-of shell identifier characters, and the value consists of a hash algorithm,
##############################################
git-2.29.2+next.20201030/t/t4067-diff-partial-clone.sh-102- # Ensure that a and another-a are fetched, and check (by successful
git-2.29.2+next.20201030/t/t4067-diff-partial-clone.sh:103: # execution of the diff) that no invalid OIDs are sent.
git-2.29.2+next.20201030/t/t4067-diff-partial-clone.sh-104- GIT_TRACE_PACKET="$(pwd)/trace" git -C client diff HEAD^ HEAD &&
##############################################
git-2.29.2+next.20201030/t/test-terminal.perl-19- close $out;
git-2.29.2+next.20201030/t/test-terminal.perl:20: exec(@$argv) or die "cannot exec '$argv->[0]': $!"
git-2.29.2+next.20201030/t/test-terminal.perl-21- }
##############################################
git-2.29.2+next.20201030/templates/Makefile-39- case "$$boilerplate" in *~) continue ;; esac && \
git-2.29.2+next.20201030/templates/Makefile:40: dst=`echo "$$boilerplate" | sed -e 's|^this|.|;s|--|/|g'` && \
git-2.29.2+next.20201030/templates/Makefile:41: dir=`expr "$$dst" : '\(.*\)/'` && \
git-2.29.2+next.20201030/templates/Makefile-42- mkdir -p blt/$$dir && \
##############################################
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-45-# Is topic fully merged to master?
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample:46:not_in_master=`git rev-list --pretty=oneline ^master "$topic"`
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-47-if test -z "$not_in_master"
##############################################
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-53-# Is topic ever merged to next? If so you should not be rebasing it.
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample:54:only_next_1=`git rev-list ^master "^$topic" ${publish} | sort`
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample:55:only_next_2=`git rev-list ^master ${publish} | sort`
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-56-if test "$only_next_1" = "$only_next_2"
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-57-then
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample:58: not_in_topic=`git rev-list "^$topic" master`
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-59- if test -z "$not_in_topic"
##############################################
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-66-else
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample:67: not_in_next=`git rev-list --pretty=oneline ^${publish} "$topic"`
git-2.29.2+next.20201030/templates/hooks--pre-rebase.sample-68- @PERL_PATH@ -e '
##############################################
git-2.29.2+next.20201030/debian/changelog.upstream-21989- am: teach mercurial patch parser how to read from stdin
git-2.29.2+next.20201030/debian/changelog.upstream:21990: parse-options-cb: implement parse_opt_passthru()
git-2.29.2+next.20201030/debian/changelog.upstream-21991- parse-options-cb: implement parse_opt_passthru_argv()
##############################################
git-2.29.2+next.20201030/debian/changelog.upstream-34166- Makefile: do not have git.o depend on common-cmds.h
git-2.29.2+next.20201030/debian/changelog.upstream:34167: Makefile: apply dependencies consistently to sparse/asm targets
git-2.29.2+next.20201030/debian/changelog.upstream-34168- Makefile: do not replace @@GIT_USER_AGENT@@ in scripts
##############################################
git-2.29.2+next.20201030/debian/changelog.upstream-67292-Serge E. Hallyn (1):
git-2.29.2+next.20201030/debian/changelog.upstream:67293: socksetup: don't return on set_reuse_addr() error
git-2.29.2+next.20201030/debian/changelog.upstream-67294-
##############################################
git-2.29.2+next.20201030/debian/changelog.upstream-67461-Serge E. Hallyn (1):
git-2.29.2+next.20201030/debian/changelog.upstream:67462: socksetup: don't return on set_reuse_addr() error
git-2.29.2+next.20201030/debian/changelog.upstream-67463-
##############################################
git-2.29.2+next.20201030/debian/examples/index.aux-generation-18-find . -name 'HEAD' | grep ^[-./=+a-zA-Z0-9]*\$ | sed s:/HEAD\$:: | while read DIR ; do
git-2.29.2+next.20201030/debian/examples/index.aux-generation:19: TREEUID=`stat -c %U $DIR`
git-2.29.2+next.20201030/debian/examples/index.aux-generation:20: TREEUSERNAME=`grep ^$TREEUID: /etc/passwd | cut -f5 -d: | sed s/\ /+/`
git-2.29.2+next.20201030/debian/examples/index.aux-generation-21- if [ "$TREEUSERNAME" = "" ]; then
##############################################
git-2.29.2+next.20201030/debian/examples/index.aux-generation-34-ls */*/HEAD | grep ^[-./=+a-zA-Z0-9]*\$ | sed s:/HEAD\$:: | while read DIR ; do
git-2.29.2+next.20201030/debian/examples/index.aux-generation:35: TREEUID=`stat -c %U $DIR`
git-2.29.2+next.20201030/debian/examples/index.aux-generation-36- TREEUSERNAME=`XXX`