Patrick Steinhardt 5bb4298acf builtin/maintenance: split into foreground and background tasks
Both git-gc(1) and git-maintenance(1) have logic to daemonize so that
the maintenance tasks are performed in the background. git-gc(1) has
some special logic though to not perform _all_ housekeeping tasks in the
background: both references and reflogs are still handled synchronously
in the foreground.

This split exists because otherwise it may easily happen that git-gc(1)
keeps the "packed-refs" file locked for an extended amount of time,
where the next Git command that wants to modify any reference could now
fail. This was especially important in the past, where git-gc(1) was
still executed directly as part of our automatic maintenance: git-gc(1)
was invoked via `git gc --auto --detach`, so we knew to handle most of
the maintenance tasks in the background while doing those parts that may
cause locking issues in the foreground.

We have since moved to git-maintenance(1), which is a more flexible
replacement for git-gc(1). By default this command runs git-gc(1), only,
but it can be configured to run different tasks, as well. This command
does not know about the split between maintenance tasks that should run
before and after detach though, and this has led to several bug reports
about spurious locking errors for the "packed-refs" file.

Prepare for a fix by introducing this split for maintenance tasks. Note
that this commit does not yet change any of the tasks, so there should
not (yet) be a change in behaviour.

Signed-off-by: Patrick Steinhardt <ps@pks.im>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2025-06-03 08:30:51 -07:00
2025-05-05 14:56:24 -07:00
2025-05-23 15:34:09 -07:00
2025-05-09 19:17:19 +02:00
2023-11-26 10:07:06 +09:00
2024-09-20 14:40:41 -07:00
2024-09-06 09:31:15 -07:00
2024-12-18 10:44:30 -08:00
2024-09-23 10:35:07 -07:00
2025-03-26 16:26:09 +09:00
2025-04-24 17:25:33 -07:00
2024-09-16 10:46:00 -07:00
2024-06-14 10:26:33 -07:00
2024-06-14 10:26:33 -07:00
2024-01-23 10:40:10 -08:00
2025-04-24 17:25:33 -07:00
2025-03-05 10:37:44 -08:00
2024-06-14 10:26:33 -07:00
2025-01-21 08:44:54 -08:00
2025-01-21 08:44:54 -08:00
2024-12-23 09:32:11 -08:00
2024-04-05 15:21:14 -07:00
2024-12-18 10:44:31 -08:00
2025-03-03 13:49:23 -08:00
2025-05-05 14:56:24 -07:00
2023-04-17 21:15:56 +02:00
2024-10-23 16:16:36 -04:00
2024-10-23 16:16:36 -04:00
2024-10-23 16:16:36 -04:00
2024-09-19 13:46:00 -07:00
2025-03-26 16:26:11 +09:00
2025-03-03 08:17:47 -08:00
2024-12-18 10:44:31 -08:00
2023-11-26 10:07:05 +09:00
2023-06-28 14:06:39 -07:00
2025-05-08 12:36:31 -07:00
2025-04-29 10:08:12 -07:00
2025-01-31 10:06:10 -08:00
2023-06-28 14:06:39 -07:00
2024-10-23 16:16:36 -04:00
2023-11-26 10:07:05 +09:00
2023-11-26 10:07:05 +09:00
2024-06-14 10:26:33 -07:00
2024-12-18 10:44:31 -08:00
2024-12-18 10:44:31 -08:00
2024-02-26 15:34:01 -08:00
2024-07-08 14:53:10 -07:00
2025-04-24 17:25:33 -07:00
2025-04-23 13:58:50 -07:00
2025-05-12 13:06:26 -07:00
2024-10-21 16:05:04 -04:00
2024-06-14 10:26:33 -07:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2025-02-03 16:12:42 -08:00
2025-02-03 16:12:42 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2023-11-26 10:07:05 +09:00
2025-03-03 13:49:19 -08:00
2024-09-19 13:46:01 -07:00
2024-04-05 15:21:14 -07:00
2025-03-26 16:26:11 +09:00
2024-06-14 10:26:33 -07:00
2024-09-19 13:46:12 -07:00
2025-05-19 16:02:47 -07:00
2024-12-18 10:44:30 -08:00
2023-11-26 10:07:05 +09:00
2024-12-27 08:12:40 -08:00
2024-09-30 11:23:03 -07:00
2024-06-14 10:26:33 -07:00
2023-09-15 17:08:46 -07:00
2025-01-13 12:55:26 -08:00
2025-01-13 12:55:26 -08:00
2024-12-23 09:32:11 -08:00
2024-05-17 10:33:39 -07:00
2025-03-03 13:49:26 -08:00
2024-12-18 10:44:30 -08:00
2024-12-18 10:44:30 -08:00
2025-03-03 13:49:27 -08:00
2025-02-06 14:56:45 -08:00
2023-06-28 14:06:39 -07:00
2025-01-17 13:30:02 -08:00
2025-05-15 17:24:55 -07:00
2024-06-14 10:26:33 -07: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
No description provided
Readme 605 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%