explain error codes NAME perror - explain error codes SYNOPSIS perror [ options ] errorcode ... D......of events that would occur but do not actually change the system. -v , --verbose Verbose; explain what is being done. -w , --warnings Enable warnings. This option has not been i…...of events that would occur but do not actually change the system. -v , --verbose Verbose; explain what is being done. -w , --warnings Enable warnings. This option has not been i…...f each existing destination file -b like --backup but does not accept an argument --debug explain how a file is copied. Implies -v --exchange exchange source and destination -f …...ts of special files when recursive -d same as --no-dereference --preserve = links --debug explain how a file is copied. Implies -v -f , --force if an existing destination file c…...s and its own process. You can toggle these on and off with the 'i' and 'a' keys. You can EXPLAIN a query from this mode with the 'e' key. This displays the query's full text, t…...ctories and their contents recursively -d , --dir remove empty directories -v , --verbose explain what is being done --help display this help and exit --version output version i…...cept the last, or all components of --target-directory , then copy SOURCE to DEST --debug explain how a file is copied. Implies -v -g , --group = GROUP set group ownership, inst…...' B C This explanation comes for "free" because there was no change. Similarly C could be explained using 1 , but that comes at some cost c>0 because of the modification: 1 ----…...a line: |A brief introduction $ | $ |$ |A new paragraph$ |# with a commented-out line $ |explaining lots of stuff.$ |$ |# An old paragraph, also commented-out. $ | $ |The end.$ …...ION While git creates a basic commit message automatically, it is strongly recommended to explain why the original commit is being reverted. In addition, repeatedly reverting re…...modification is different. This is usually a good choice. -v , --verbose Verbose output, explain to the user what is being done. If specified once, every hardlinked file is disp…...does not match the signal being used to kill it, the capsh program exits with status 1. --explain= cap_xxx Give a brief textual description of what privileges the specified capa…...ges" section of gitrevisions (7). [--] <path>... Consider only commits that are enough to explain how the files that match the specified paths came to be. Paths may need to be p…...being pruned by issuing the git worktree lock command, optionally specifying --reason to explain why the worktree is locked. COMMANDS add <path> [<commit-ish>] Create a worktree…...f lines with the format <mode> <object> <stage> <filename> The filename will be quoted as explained for the configuration variable core.quotePath (see git-config (1)). However, …...w timezones NAME tzselect - view timezones SYNOPSIS tzselect DESCRIPTION This manual page explains how you can use the tzselect utility to view the installed timezone. It comes …...he activities of update-alternatives are quite involved, some specific terms will help to explain its operation. generic name (or alternative link) A name, like /usr/bin/editor …..."--brief" If the -b option is given, "gprof" doesn't print the verbose blurbs that try to explain the meaning of all of the fields in the tables. This is useful if you intend to…..."--brief" If the -b option is given, "gprof" doesn't print the verbose blurbs that try to explain the meaning of all of the fields in the tables. This is useful if you intend to…