Jeff King 4e10738a93 Allow per-command pager config
There is great debate over whether some commands should set
up a pager automatically. This patch allows individuals to
set their own pager preferences for each command, overriding
the default. For example, to disable the pager for git
status:

  git config pager.status false

If "--pager" or "--no-pager" is specified on the command
line, it takes precedence over the config option.

There are two caveats:

  - you can turn on the pager for plumbing commands.
    Combined with "core.pager = always", this will probably
    break a lot of things. Don't do it.

  - This only works for builtin commands. The reason is
    somewhat complex:

    Calling git_config before we do setup_git_directory
    has bad side effects, because it wants to know where
    the git_dir is to find ".git/config". Unfortunately,
    we cannot call setup_git_directory indiscriminately,
    because some builtins (like "init") break if we do.

    For builtins, this is OK, since we can just wait until
    after we call setup_git_directory. But for aliases, we
    don't know until we expand (recursively) which command
    we're doing. This should not be a huge problem for
    aliases, which can simply use "--pager" or "--no-pager"
    in the alias as appropriate.

    For external commands, however, we don't know we even
    have an external command until we exec it, and by then
    it is too late to check the config.

    An alternative approach would be to have a config mode
    where we don't bother looking at .git/config, but only
    at the user and system config files. This would make the
    behavior consistent across builtins, aliases, and
    external commands, at the cost of not allowing per-repo
    pager config for at all.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-07-06 02:20:24 -07:00
2007-06-07 00:04:01 -07:00
2008-07-05 18:33:16 -07:00
2008-05-26 19:10:43 -07:00
2008-06-25 13:19:53 -07:00
2007-06-07 00:04:01 -07:00
2007-06-07 00:04:01 -07:00
2008-07-02 21:57:52 -07:00
2008-07-05 10:43:46 -07:00
2007-05-30 15:03:50 -07:00
2007-06-07 00:04:01 -07:00
2008-07-05 18:33:16 -07:00
2008-05-25 14:25:02 -07:00
2008-05-25 14:25:02 -07:00
2008-03-14 00:16:42 -07:00
2008-05-25 14:25:02 -07:00
2008-06-06 09:21:48 -07:00
2008-05-26 19:49:01 -07:00
2008-07-02 21:57:52 -07:00
2008-06-25 13:19:49 -07:00
2007-06-07 00:04:01 -07:00
2008-07-05 18:33:16 -07:00
2008-05-26 22:38:19 -07:00
2007-06-07 00:04:01 -07:00
2008-05-10 18:14:28 -07:00
2008-02-05 00:46:49 -08:00
2008-07-02 21:57:52 -07:00
2008-03-05 10:32:01 -08:00
2008-02-25 23:57:35 -08:00
2008-07-02 21:57:52 -07:00
2008-05-27 22:34:19 -07:00
2008-07-06 02:20:24 -07:00
2008-05-25 14:25:02 -07:00
2008-07-02 21:57:52 -07:00
2008-05-06 16:50:17 -07:00
2008-07-05 10:43:46 -07:00
2007-12-13 23:04:26 -08:00
2008-02-09 23:16:51 -08:00
2008-02-25 23:57:35 -08:00
2007-06-07 00:04:01 -07:00
2008-06-26 08:47:15 +02:00
2008-06-22 18:39:37 -07:00
2007-06-07 00:04:01 -07:00
2008-06-22 14:34:20 -07:00
2008-05-25 13:41:37 -07:00
2008-07-01 17:09:21 -07:00
2008-05-25 13:41:37 -07:00
2007-11-09 21:14:10 -08:00
2008-07-02 21:57:52 -07:00
2008-02-25 19:57:06 -08:00
2008-03-02 15:11:07 -08:00
2007-05-01 02:59:08 -07:00
2008-07-05 18:33:16 -07:00
2008-03-02 15:11:07 -08:00
2008-03-14 00:16:42 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, depending on your mood.

 - random three-letter combination that is pronounceable, and not
   actually used by any common UNIX command.  The fact that it is a
   mispronunciation of "get" may or may not be relevant.
 - stupid. contemptible and despicable. simple. Take your pick from the
   dictionary of slang.
 - "global information tracker": you're in a good mood, and it actually
   works for you. Angels sing, and a light suddenly fills the room.
 - "goddamn idiotic truckload of sh*t": when it breaks

Git is a fast, scalable, distributed revision control system with an
unusually rich command set that provides both high-level operations
and full access to internals.

Git is an Open Source project covered by the GNU General Public License.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.
See Documentation/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
including full documentation and Git related tools.

The user discussion and development of Git take place on the Git
mailing list -- everyone is welcome to post bug reports, feature
requests, comments and patches to git@vger.kernel.org. To subscribe
to the list, send an email with just "subscribe git" in the body to
majordomo@vger.kernel.org. The mailing list archives are available at
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%