Patrick Steinhardt 91c5a5e000 t1300: make tests more robust with non-default ref backends
The t1300 test suite exercises the git-config(1) tool. To do so, the
test overwrites ".git/config" to contain custom contents in several
places with code like the following:

```
cat > .git/config <<\EOF
...
EOF
```

While this is easy enough to do, it may create problems when using a
non-default repository format because this causes us to overwrite the
repository format version as well as any potential extensions. With the
upcoming "reftable" ref backend the result is that Git would try to
access refs via the "files" backend even though the repository has been
initialized with the "reftable" backend, which will cause failures when
trying to access any refs.

Ideally, we would rewrite the whole test suite to not depend on state
written by previous tests, but that would result in a lot of changes in
this test suite. Instead, we only refactor tests which access the refdb
to be more robust by using their own separate repositories, which allows
us to be more careful and not discard required extensions.

Note that we also have to touch up how the CUSTOM_CONFIG_FILE gets
accessed. This environment variable contains the relative path to a
custom config file which we're setting up. But because we are now using
subrepositories, this relative path will not be found anymore because
our working directory changes. This issue is addressed by storing the
absolute path to the file in CUSTOM_CONFIG_FILE instead.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Reviewed-by: Christian Couder <christian.couder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2024-01-29 13:54:32 -08:00
2023-11-03 18:52:02 +09:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:24 -08:00
2023-11-26 10:07:05 +09:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2023-11-26 10:07:06 +09:00
2024-01-08 14:05:15 -08:00
2023-11-10 08:15:32 +09:00
2023-11-26 10:10:48 +09:00
2023-11-09 18:56:10 +09:00
2024-01-08 14:05:15 -08:00
2023-10-30 07:09:55 +09:00
2024-01-08 14:05:15 -08:00
2023-12-26 12:04:32 -08:00
2023-12-26 12:04:32 -08:00
2023-11-26 10:10:48 +09:00
2023-07-25 12:05:24 -07:00
2023-11-26 10:10:48 +09:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2023-07-06 11:54:48 -07:00
2023-04-10 08:46:40 -07:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2023-08-31 15:51:07 -07:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2023-08-31 15:51:07 -07:00
2023-04-17 21:15:56 +02:00
2023-11-26 10:07:05 +09:00
2023-12-09 16:37:51 -08:00
2023-11-26 10:10:48 +09:00
2023-11-26 10:07:05 +09:00
2023-06-28 14:06:39 -07:00
2023-12-26 12:04:32 -08:00
2024-01-08 14:05:15 -08:00
2023-12-26 12:04:32 -08:00
2023-06-28 14:06:39 -07:00
2024-01-08 14:05:15 -08:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-12-28 12:22:43 -08:00
2023-06-21 13:39:54 -07:00
2023-11-09 19:07:52 +09:00
2024-01-08 14:05:15 -08:00
2023-10-23 13:56:36 -07:00
2023-06-28 14:06:39 -07:00
2023-06-12 13:49:36 -07:00
2023-11-26 10:07:05 +09:00
2023-09-15 17:08:46 -07:00
2024-01-08 14:05:15 -08:00
2023-11-26 10:07:05 +09:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2024-01-02 13:51:30 -08:00
2023-12-15 14:08:28 -08:00
2023-12-09 16:37:51 -08:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2024-01-08 14:05:15 -08:00
2023-11-26 10:07:05 +09:00
2022-12-01 18:38:07 +09:00
2023-12-27 14:52:24 -08:00
2023-09-15 17:08:46 -07:00
2024-01-08 14:05:15 -08:00
2023-11-26 10:07:05 +09:00
2023-03-17 14:03:09 -07:00
2024-01-02 13:51:29 -08:00
2023-06-28 14:06:39 -07:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2023-04-04 14:28:27 -07:00
2023-05-17 10:11:41 -07:00
2024-01-02 13:51:30 -08:00

Build status

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-<commandname>.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 and Documentation/CodingGuidelines).

Those wishing to help with error message, usage and informational message string translations (localization l10) should see po/README.md (a po file is a Portable Object file that holds the translations).

To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org (not the Git list). The mailing list archives are available at https://lore.kernel.org/git/, https://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%