error(_("unknown non-ascii option in string: `%s'"), ctx.argv[0]); } usage_with_options(usagestr, options); } precompose_argv_prefix(argc, argv, NULL); free_preprocessed_options(real_options); free(ctx.alias_groups); for (struct parse_opt_cmdmode_list *elem = ctx.cmdmo...
error(_("unknown non-ascii option in string: `%s'"), ctx.argv[0]); } usage_with_options(usagestr, options); }precompose_argv_prefix(argc, argv, NULL); free_preprocessed_options(real_options); free(ctx.alias_groups); return parse_options_end(&ctx); ...
This command will fail with non-zero status upon error. Some exit codes are: The section or key is invalid (ret=1), no section or name was provided (ret=2), the config file is invalid (ret=3), the config file cannot be written (ret=4), you try to unset an option which...
Run as if git was started in<path>instead of the current working directory. When multiple-Coptions are given, each subsequent non-absolute-C <path>is interpreted relative to the preceding-C <path>. If<path>is present but empty, e.g.-C "", then the current working directory is left un...
* "git mv A B" in a sparsely populated working tree can be asked to move a path between directories that are "in cone" (i.e. expected to be materialized in the working tree) and "out of cone" (i.e. expected to be hidden). The handling of such cases has been ...
osx-keychain (in contrib/). * Workaround for a false positive compiler warning. * "git p4" working on UTF-16 files on Windows did not implement CRLF-to-LF conversion correctly, which has been corrected. * "git p4" did not handle non-ASCII client name well, which has been ...
We read every piece of feedback, and take your input very seriously. Include my email address so I can be contacted Cancel Submit feedback Saved searches Use saved searches to filter your results more quickly Cancel Create saved search Sign in Sign up Reseting focus {...
--encoding=<encoding> The commit objects record the encoding used for the log message in their encoding header; this option can be used to tell the command to re-code the commit log message in the encoding preferred by the user. For non plumbing commands this defaults to UTF-8. Note ...
* Giving --format-patch option if you mean a range.EOF } catch Git::Error::Command with { # Not a valid revision. Treat it as a filename.return 0; } } # Now that all the defaults are set, process the rest of the command line # arguments and collect up the files that ...
--encoding[=<encoding>] The commit objects record the encoding used for the log message in their encoding header; this option can be used to tell the command to re-code the commit log message in the encoding preferred by the user. For non plumbing commands this defaults to UTF-8. --...