Toll Free Numbers
  • Last 5 Forum Topics
    Last post

The Web Only This Site



  • MARC

    Mailing list ARChives
    - Search by -


    Computing Dictionary

  • Text Link Ads
  • LINUX man pages
  • Linux Man Page Viewer

    The following form allows you to view linux man pages.





           git apply [--stat] [--numstat] [--summary] [--check] [--index]
                     [--apply] [--no-add] [--build-fake-ancestor=<file>] [-R | --reverse]
                     [--allow-binary-replacement | --binary] [--reject] [-z]
                     [-pNUM] [-CNUM] [--inaccurate-eof] [--recount] [--cached]
                     [--ignore-space-change | --ignore-whitespace ]
                     [--exclude=PATH] [--include=PATH] [--directory=<root>]
                     [--verbose] [<patch>...]


           Reads the supplied diff output (i.e. "a patch") and applies it to
           files. With the --index option the patch is also applied to the index,
           and with the --cache option the patch is only applied to the index.
           Without these options, the command applies the patch only to files, and
           does not require them to be in a git repository.


               The files to read the patch from.  - can be used to read from the
               standard input.
               Instead of applying the patch, output diffstat for the input. Turns
               off "apply".
               Similar to --stat, but shows the number of added and deleted lines
               in decimal notation and the pathname without abbreviation, to make
               it more machine friendly. For binary files, outputs two - instead
               of saying 0 0. Turns off "apply".
               Instead of applying the patch, output a condensed summary of
               information obtained from git diff extended headers, such as
               creations, renames and mode changes. Turns off "apply".
               Instead of applying the patch, see if the patch is applicable to
               the current working tree and/or the index file and detects errors.
               Turns off "apply".
               When --check is in effect, or when applying the patch (which is the
               default when none of the options that disables it is in effect),
               make sure the patch is applicable to what the current index file
               records. If the file to be patched in the working tree is not
               up-to-date, it is flagged as an error. This flag also causes the
               index file to be updated.
           -R, --reverse
               Apply the patch in reverse.
               For atomicity, git apply by default fails the whole patch and does
               not touch the working tree when some of the hunks do not apply.
               This option makes it apply the parts of the patch that are
               applicable, and leave the rejected hunks in corresponding *.rej
               When --numstat has been given, do not munge pathnames, but use a
               NUL-terminated machine-readable format.
               Without this option, each pathname output will have TAB, LF, double
               quotes, and backslash characters replaced with \t, \n, \", and \\,
               respectively, and the pathname will be enclosed in double quotes if
               any of those replacements occurred.
               Remove <n> leading slashes from traditional diff paths. The default
               is 1.
               Ensure at least <n> lines of surrounding context match before and
               after each change. When fewer lines of surrounding context exist
               they all must match. By default no context is ever ignored.
               By default, git apply expects that the patch being applied is a
               unified diff with at least one line of context. This provides good
               safety measures, but breaks down when applying a diff generated
               with --unified=0. To bypass these checks use --unidiff-zero.
               Note, for the reasons stated above usage of context-free patches is
               If you use any of the options marked "Turns off apply" above, git
               apply reads and outputs the requested information without actually
               applying the patch. Give this flag after those flags to also apply
               the patch.
               When applying a patch, ignore additions made by the patch. This can
               be used to extract the common part between two files by first
               running diff on them and applying the result with this option,
               which would apply the deletion part but not the addition part.
           --allow-binary-replacement, --binary
               Historically we did not allow binary patch applied without an
               When --exclude and --include patterns are used, they are examined
               in the order they appear on the command line, and the first match
               determines if a patch to each path is used. A patch to a path that
               does not match any include/exclude pattern is used by default if
               there is no include pattern on the command line, and ignored if
               there is any include pattern.
           --ignore-space-change, --ignore-whitespace
               When applying a patch, ignore changes in whitespace in context
               lines if necessary. Context lines will preserve their whitespace,
               and they will not undergo whitespace fixing regardless of the value
               of the --whitespace option. New lines will still be fixed, though.
               When applying a patch, detect a new or modified line that has
               whitespace errors. What are considered whitespace errors is
               controlled by core.whitespace configuration. By default, trailing
               whitespaces (including lines that solely consist of whitespaces)
               and a space character that is immediately followed by a tab
               character inside the initial indent of the line are considered
               whitespace errors.
               By default, the command outputs warning messages but applies the
               patch. When git-apply is used for statistics and not applying a
               patch, it defaults to nowarn.
               You can use different <action> values to control this behavior:
               ?    nowarn turns off the trailing whitespace warning.
               ?    warn outputs warnings for a few such errors, but applies the
                   patch as-is (default).
               ?    fix outputs warnings for a few such errors, and applies the
                   patch after fixing them (strip is a synonym --- the tool used
                   to consider only trailing whitespace characters as errors, and
                   the fix involved stripping them, but modern gits do more).
               ?    error outputs warnings for a few such errors, and refuses to
                   apply the patch.
               ?    error-all is similar to error but shows all errors.
               Under certain circumstances, some versions of diff do not correctly
               detect a missing new-line at the end of the file. As a result,
               patches created by such diff programs do not record incomplete
               lines correctly. This option adds support for applying such patches
               by working around this bug.
           -v, --verbose
               Report progress to stderr. By default, only a message about the
               modules/git-gui/ by running git apply


               Set to change if you want changes in whitespace to be ignored by
               default. Set to one of: no, none, never, false if you want changes
               in whitespace to be significant.
               When no --whitespace flag is given from the command line, this
               configuration item is used as the default.


           If the patch contains any changes to submodules then git apply treats
           these changes as follows.
           If --index is specified (explicitly or implicitly), then the submodule
           commits must match the index exactly for the patch to apply. If any of
           the submodules are checked-out, then these check-outs are completely
           ignored, i.e., they are not required to be up-to-date or clean and they
           are not updated.
           If --index is not specified, then the submodule commits in the patch
           are ignored and only the absence or presence of the corresponding
           subdirectory is checked and (if possible) updated.


           Written by Linus Torvalds <[1]>


           Documentation by Junio C Hamano


           Part of the git(1) suite



    Git 1.7.1 03/04/2013 GIT-APPLY(1)


  • Linux

    The Distributions


    The Software


    The News


  • Toll Free

Toll Free Numbers
Copyright © 1999 - 2016 by LinuxGuruz