Junio C Hamano ce46a1ca14 Merge branch 'js/adjust-tests-to-explicitly-access-bare-repo' into seen
Some tests assume that bare repository accesses are by default
allowed; rewrite some of them to avoid the assumption, rewrite
others to explicitly set safe.bareRepository to allow them.

Comments?

* js/adjust-tests-to-explicitly-access-bare-repo:
  git p4 clone --bare: need to be explicit about the gitdir
  t9700: stop relying on implicit bare repo discovery
  t9210: pass `safe.bareRepository=all` to `scalar register`
  t6020: use `-C` for worktree, `--git-dir` for bare repository
  t5619: wrap `test_commit_bulk` in `GIT_DIR` subshell for bare repo
  t5540/t5541: avoid accessing a bare repository via `-C <dir>`
  t5509: specify bare repository path explicitly
  t5505: export `GIT_DIR` after `git init --bare`
  t5503: avoid discovering a bare repository
  t2406: use `--git-dir=.` for bare repository worktree repair
  t2400: explicitly specify bare repo for `git worktree add`
  t1900: avoid using `-C <dir>` for a bare repository
  t1020: use `--git-dir` instead of subshell for bare repo
  t0056: allow implicit bare repo discovery for `-C` work-tree tests
  t0003: use `--git-dir` for bare repo attribute tests
  t0001: replace `cd`+`git` with `git --git-dir` in `check_config`
  t0001: allow implicit bare repo discovery for aliased-command test
2026-04-09 15:11:51 -07:00
2026-03-27 11:00:01 -07:00
2026-02-03 09:41:52 -08:00
2026-04-01 10:28:19 -07:00
2025-08-02 22:44:58 -07:00
2025-07-01 07:46:22 -07:00
2026-03-20 09:31:04 +08:00
2026-03-16 11:21:09 -07:00
2025-12-07 07:28:13 +09:00
2026-03-23 09:20:29 -07:00
2026-02-07 17:41:03 -08:00
2026-02-09 12:09:09 -08:00
2026-02-23 13:23:41 -08:00
2026-02-23 13:23:41 -08:00
2026-04-06 09:18:52 -07:00
2026-03-24 12:31:32 -07:00
2026-03-23 09:20:29 -07:00
2025-09-12 08:59:52 -07:00
2026-04-08 10:19:17 -07:00
2026-03-23 08:33:10 -07:00
2026-03-23 08:33:10 -07:00
2026-04-08 08:21:34 -07:00
2026-04-06 09:18:52 -07:00
2026-02-17 13:30:41 -08:00
2025-07-23 08:15:18 -07:00
2026-03-31 20:43:14 -07:00
2025-11-25 12:15:59 -08:00
2025-11-25 12:15:59 -08:00
2026-02-23 13:21:18 -08:00
2025-07-15 15:18:18 -07:00
2026-04-08 10:19:17 -07:00
2026-03-26 09:38:06 -07:00
2026-03-26 09:38:06 -07:00
2026-02-08 15:03:06 -08:00
2025-08-21 13:46:59 -07:00
2026-03-09 14:36:55 -07:00
2025-11-04 07:48:07 -08:00
2026-03-31 20:43:14 -07:00
2025-08-21 13:46:58 -07:00
2026-03-23 21:27:17 -07:00
2026-02-05 15:42:01 -08:00
2026-04-08 10:19:18 -07:00
2026-03-31 20:43:14 -07:00
2026-03-29 19:13:12 -07:00
2026-03-29 19:13:12 -07:00
2025-12-29 22:02:54 +09:00
2026-01-09 18:36:17 -08:00
2026-01-09 18:36:17 -08:00
2026-02-08 15:16:49 -08:00
2026-02-08 15:16:49 -08:00
2026-03-31 20:43:14 -07:00
2025-11-12 14:04:04 -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.adoc to get started, then see Documentation/giteveryday.adoc for a useful minimum set of commands, and Documentation/git-<commandname>.adoc 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.adoc (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 to git+subscribe@vger.kernel.org (see https://subspace.kernel.org/subscribing.html for details). 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
A fork of Git containing Windows-specific patches.
Readme 529 MiB
2025-08-19 03:50:05 -05:00
Languages
C 51.5%
Shell 37.6%
Perl 4.2%
Tcl 3%
Python 0.8%
Other 2.7%