Peng Yu <> writes:
> Hi, git-annex has a set of COMMON OPTIONS options (they are applicable
> to all git-annex commands). Is there something similar for git?

The 'git' manual page on my system includes this section, which appears
to be the common options for git:

           Prints the Git suite version that the git program came from.

           Prints the synopsis and a list of the most commonly used commands.
           If the option --all or -a is given then all available commands are
           printed. If a Git command is named this option will bring up the
           manual page for that command.

           Other options are available to control how the manual page is
           displayed. See git-help(1) for more information, because git --help
           ...  is converted internally into git help ....

       -c <name>=<value>
           Pass a configuration parameter to the command. The value given will
           override values from configuration files. The <name> is expected in
           the same format as listed by git config (subkeys separated by

           Path to wherever your core Git programs are installed. This can
           also be controlled by setting the GIT_EXEC_PATH environment
           variable. If no path is given, git will print the current setting
           and then exit.

           Print the path, without trailing slash, where Git's HTML
           documentation is installed and exit.

           Print the manpath (see man(1)) for the man pages for this version
           of Git and exit.

           Print the path where the Info files documenting this version of Git
           are installed and exit.

       -p, --paginate
           Pipe all output into less (or if set, $PAGER) if standard output is
           a terminal. This overrides the pager.<cmd> configuration options
           (see the "Configuration Mechanism" section below).

           Do not pipe Git output into a pager.

           Set the path to the repository. This can also be controlled by
           setting the GIT_DIR environment variable. It can be an absolute
           path or relative path to current working directory.

           Set the path to the working tree. It can be an absolute path or a
           path relative to the current working directory. This can also be
           controlled by setting the GIT_WORK_TREE environment variable and
           the core.worktree configuration variable (see core.worktree in git-
           config(1) for a more detailed discussion).

           Set the Git namespace. See gitnamespaces(7) for more details.
           Equivalent to setting the GIT_NAMESPACE environment variable.

           Treat the repository as a bare repository. If GIT_DIR environment
           is not set, it is set to the current working directory.

           Do not use replacement refs to replace Git objects. See git-
           replace(1) for more information.

           Treat pathspecs literally, rather than as glob patterns. This is
           equivalent to setting the GIT_LITERAL_PATHSPECS environment
           variable to 1.


You received this message because you are subscribed to the Google Groups "Git 
for human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
For more options, visit

Reply via email to