The Linux Manuals (man pages) document is an important part of Linux documents. Linux Manuals are organized as several sections. Each section has a group of commands for a specific area in Linux usage, administration or development.
git-show-index – Show packed archive index Synopsisgit show-index [–object-format=<hash-algorithm>]DescriptionRead the .idx file for a Git packfile (created with git-pack-objects(1) or git-index-pack(1)) from the standard input, and dump its contents. The output consists of one object per line, with each line containing two or three space-separated columns: • the first column is the offset in bytes…
git-show-branch – Show branches and their commits Synopsisgit show-branch [-a|–all] [-r|–remotes] [–topo-order | –date-order] [–current] [–color[=<when>] | –no-color] [–sparse] [–more=<n> | –list | –independent | –merge-base] [–no-name | –sha1-name] [–topics] [(<rev> | <glob>)…] git show-branch (-g|–reflog)[=<n>[,<base>]] [–list] [<ref>]DescriptionShows the commit ancestry graph starting from the commits named with <rev>s or <glob>s (or all refs under…
git-shortlog – Summarize ‘git log’ output Synopsisgit shortlog [<options>] [<revision range>] [[–] <path>…] git log –pretty=short | git shortlog [<options>]DescriptionSummarizes git log output in a format suitable for inclusion in release announcements. Each commit will be grouped by author and title. Additionally, "[PATCH]" will be stripped from the commit description. If no revisions are passed…
git-shell – Restricted login shell for Git-only SSH access Synopsischsh -s $(command -v git-shell) <user> git clone <user>@localhost:/path/to/repo.git ssh <user>@localhostDescriptionThis is a login shell for SSH accounts to provide restricted Git access. It permits execution only of server-side Git commands implementing the pull/push functionality, plus custom commands present in a subdirectory named git-shell-commands in the…
git-sh-setup – Common Git shell script setup code Synopsis. "$(git –exec-path)/git-sh-setup"DescriptionThis is not a command the end user would want to run. Ever. This documentation is meant for people who are studying the Porcelain-ish scripts and/or are writing new ones. The git sh-setup scriptlet is designed to be sourced (using .) by other shell scripts…
git-sh-i18n – Git’s i18n setup code for shell scripts Synopsis. "$(git –exec-path)/git-sh-i18n"DescriptionThis is not a command the end user would want to run. Ever. This documentation is meant for people who are studying the Porcelain-ish scripts and/or are writing new ones. The ‘git sh-i18n scriptlet is designed to be sourced (using .) by Git’s porcelain…
git-sh-i18n–envsubst – Git’s own envsubst(1) for i18n fallbacks Synopsiseval_gettext () { printf "%s" "$1" | ( export PATH $(git sh-i18n–envsubst –variables "$1"); git sh-i18n–envsubst "$1" ) }DescriptionThis is not a command the end user would want to run. Ever. This documentation is meant for people who are studying the plumbing scripts and/or are writing new…
git-setup – Set up a git repository Synopsisgit-setup [<directory>] DescriptionSet up a git repository if one doesn’t exist, add all files and make an initial commit. Options<directory> The name of a new directory to setup. By default, the current working directory. Examples$ git setup path/to/repositoryAuthorWritten by Aggelos Orfanakos <agorf [at] agorf.gr> Reporting Bugs<https://github.com/tj/git-extras/issues> See Also<https://github.com/tj/git-extras>
git-send-pack – Push objects over Git protocol to another repository Synopsisgit send-pack [–dry-run] [–force] [–receive-pack=<git-receive-pack>] [–verbose] [–thin] [–atomic] [–[no-]signed|–signed=(true|false|if-asked)] [<host>:]<directory> (–all | <ref>…)DescriptionUsually you would want to use git push, which is a higher-level wrapper of this command, instead. See git-push(1). Invokes git-receive-pack on a possibly remote repository, and updates it from the current repository,…
git-send-email – Send a collection of patches as emails Synopsisgit send-email [options] <file|directory|rev-list options>…DescriptionTakes the patches given on the command line and emails them out. Patches can be specified as files, directories (which will send all files in the directory), or directly as a revision list. In the last case, any format accepted by git-format-patch(1)…
git-send-bugzilla – Attach patches to a bugzilla bug Synopsisgit-send-bugzilla [OPTIONS] (–dry-run | <bugid>) <since>[..<until>]DescriptionAttach each commit between <since> and <until> to the bug <bugid> on GNOMEcqs bugzilla. If ..<until> is not specified, the head of the current working tree is implied. If -n (or bugzilla.numbered in the repository configuration) is specified, instead of "[PATCH] Subject",…
git-sed – replace patterns in git-controlled files Synopsisgit-sed [ -c ] [ -f flags ] search replacement DescriptionRun git grep and then send results to sed for replacement with the given flags, if -f is provided. Also runs git commit if -c is provided. Options-c commit the resulting changes with a standard commit message detailing…
git-scp – Copy files to SSH compatible git-remote Synopsis`git scp` -h|help|? `git scp` <remote> [<commits>…|<path>…] `git rscp` <remote> <path>DescriptionA convenient way to copy files from the current working tree to the working directory of a remote repository. If a <commits>… is provided, only files that has changed within the commit range will be copied. Internally…
git-root – show path of root Synopsisgit root OPTIONS Descriptionprint the path for the root directory of git repo Options-r, –relative show the relative path from root directory to current directory Examples$ cd …/git-extras/bin $ git root -r bin/ $ git root /home/…/git-extras $ cd `git root` $ pwd /home/…/git-extras # then we can $…
git-rm – Remove files from the working tree and from the index Synopsisgit rm [-f | –force] [-n] [-r] [–cached] [–ignore-unmatch] [–quiet] [–pathspec-from-file=<file> [–pathspec-file-nul]] [–] [<pathspec>…]DescriptionRemove files matching pathspec from the index, or from the working tree and the index. git rm will not remove a file from just your working directory. (There is no…
git-review – Submit changes to Gerrit for review Synopsis[-r remote ] [-uv ] –d change [branch ] [-r remote ] [-uv ] –x change [branch ] [-r remote ] [-uv ] –N change [branch ] [-r remote ] [-uv ] –X change [branch ] [-r remote ] [-uv ] –m change-ps-range [branch ] [-r remote…
git-revert – Revert some existing commits Synopsisgit revert [–[no-]edit] [-n] [-m parent-number] [-s] [-S[<keyid>]] <commit>… git revert (–continue | –skip | –abort | –quit)DescriptionGiven one or more existing commits, revert the changes that the related patches introduce, and record some new commits that record them. This requires your working tree to be clean (no modifications…
git-rev-parse – Pick out and massage parameters Synopsisgit rev-parse [<options>] <args>…DescriptionMany Git porcelainish commands take mixture of flags (i.e. parameters that begin with a dash –) and parameters meant for the underlying git rev-list command they use internally and flags and parameters for the other commands they use downstream of git rev-list. This command is…
git-rev-list – Lists commit objects in reverse chronological order Synopsisgit rev-list [<options>] <commit>… [[–] <path>…]DescriptionList commits that are reachable by following the parent links from the given commit(s), but exclude commits that are reachable from the one(s) given with a ^ in front of them. The output is given in reverse chronological order by default….
git-restore – Restore working tree files Synopsisgit restore [<options>] [–source=<tree>] [–staged] [–worktree] [–] <pathspec>… git restore [<options>] [–source=<tree>] [–staged] [–worktree] –pathspec-from-file=<file> [–pathspec-file-nul] git restore (-p|–patch) [<options>] [–source=<tree>] [–staged] [–worktree] [–] [<pathspec>…]DescriptionRestore specified paths in the working tree with some contents from a restore source. If a path is tracked but does not exist in the…