Martin Ågren cd878a206e t7006: add tests for how git config paginates
The next couple of commits will change how `git config` handles
`pager.config`, similar to how de121ffe5 (tag: respect `pager.tag` in
list-mode only, 2017-08-02) and ff1e72483 (tag: change default of
`pager.tag` to "on", 2017-08-02) changed `git tag`. Similar work has
also been done to `git branch`.

Add tests in this area to make sure that we don't regress and so that
the upcoming commits can be made clearer by adapting the tests. Add
tests for simple config-setting, `--edit`, `--get`, `--get-urlmatch`,
`get-all`, and `--list`. Those represent a fair portion of the various
options that will be affected by the next two commits.

Use `test_expect_failure` to document that we currently respect the
pager-configuration with `--edit`. The current behavior is buggy since
the pager interferes with the editor and makes the end result completely
broken. See also b3ee740c8 (t7006: add tests for how git tag paginates,
2017-08-02).

The next commit will teach simple config-setting and `--get` to ignore
`pager.config`. Test the current behavior as "success", not "failure",
since the currently expected behavior according to documentation would
be to page. The next commit will change that expectation by updating the
documentation on `git config` and will redefine those successful tests.

Remove the test added in commit 3ba7e6e29a (config: run
setup_git_directory_gently() sooner, 2010-08-05) since it has some
overlap with these. We could leave it or tweak it, or place new tests
like these next to it, but let's instead make the tests for `git config`
as similar as possible to the ones for `git tag` and `git branch`, and
place them after those.

Signed-off-by: Martin Ågren <martin.agren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-02-21 14:27:27 -08:00
2017-11-21 14:07:50 +09:00
2018-01-23 13:21:10 -08:00
2018-01-15 07:47:30 +01:00
2017-07-06 18:14:44 -07:00
2017-06-24 14:28:41 -07:00
2017-06-24 14:28:41 -07:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2017-03-13 15:28:54 -07:00
2017-11-15 12:14:28 +09:00
2017-05-25 13:08:23 +09:00
2017-05-08 15:12:57 +09:00
2017-05-08 15:12:57 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-08-03 11:08:10 -07:00
2018-01-23 13:16:36 -08:00
2017-05-02 10:46:41 +09:00
2017-11-06 13:11:21 +09:00
2016-05-09 12:29:08 -07:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2017-01-25 14:42:37 -08:00
2018-01-23 13:16:36 -08:00
2016-05-09 12:29:08 -07:00
2017-06-24 14:28:41 -07:00
2014-12-12 14:31:42 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2014-03-31 15:29:27 -07:00
2017-12-13 13:28:54 -08:00
2018-01-23 13:16:37 -08:00
2018-01-23 13:16:37 -08:00
2017-12-27 11:16:21 -08:00
2017-12-27 11:16:21 -08:00
2017-11-21 14:07:50 +09:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2018-01-21 21:14:25 -08:00
2017-11-28 13:41:50 +09:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2017-11-01 10:35:39 +09:00
2017-08-23 15:12:07 -07:00
2017-06-24 14:28:41 -07:00
2016-02-22 14:51:09 -08:00
2017-01-30 14:17:00 -08:00
2017-12-28 14:08:50 -08:00
2017-09-06 17:19:54 +09:00
2018-01-09 14:32:53 -08:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-11-09 14:31:27 +09:00
2017-12-28 13:50:05 -08:00
2018-01-23 13:16:36 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2017-01-30 14:17:00 -08:00
2017-08-23 15:12:07 -07:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2017-10-28 10:18:40 +09:00
2017-12-13 11:14:25 -08:00
2017-12-06 09:23:44 -08:00
2017-10-17 10:51:29 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2016-07-19 13:22:17 -07:00
2017-11-27 11:06:37 +09:00
2018-01-21 21:14:25 -08:00
2017-09-25 15:24:06 +09:00
2016-04-25 15:17:15 -07:00
2018-01-23 13:16:36 -08:00
2017-03-31 08:33:56 -07:00
2017-12-19 11:33:58 -08:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2017-06-24 14:28:41 -07:00
2006-03-25 16:35:43 -08:00
2017-08-26 22:55:04 -07:00
2017-06-24 14:28:41 -07:00
2014-09-02 13:28:44 -07:00
2017-12-06 09:23:44 -08:00
2016-02-22 10:40:35 -08:00
2017-11-06 14:24:27 +09:00

Git - fast, scalable, distributed revision control system

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 version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

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 (read Documentation/SubmittingPatches for instructions on patch submission). 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 https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
No description provided
Readme 598 MiB
Languages
C 50.4%
Shell 38.7%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.4%