Nguyễn Thái Ngọc Duy 327864aaf7 worktree prune: improve prune logic when worktree is moved
Automatic detection of worktree relocation by a user (via 'mv', for
instance) was removed by 618244e160 (worktree: stop supporting moving
worktrees manually - 2016-01-22). Prior to that,
.git/worktrees/<tag>/gitdir was updated whenever the worktree was
accessed in order to let the pruning logic know that the worktree was
"active" even if it disappeared for a while (due to being located on
removable media, for instance).

"git worktree move" has come so we don't really need this, but since
it's easy to do, perhaps we could keep supporting manual worktree move
a bit longer. Notice that when a worktree is active, the "index" file
should be updated pretty often in common case. The logic is updated to
check for index mtime to see if the worktree is alive.

The old logic of checking gitdir's mtime is dropped because nobody
updates it anyway. The new corner case is, if the index file does not
exist, we immediately remove the stale worktree. But if the "index"
file does not exist, you may have a bigger problem.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-03-15 12:37:48 -07:00
2017-11-21 14:07:50 +09:00
2018-02-28 13:37:52 -08:00
2018-03-15 12:37:47 -07: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
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
2017-05-02 10:46:41 +09:00
2018-02-15 14:55:43 -08:00
2018-02-15 14:55:47 -08:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2018-02-15 14:55:43 -08:00
2018-02-13 13:39:08 -08:00
2018-02-13 13:39:04 -08:00
2018-02-15 14:55:43 -08:00
2017-06-24 14:28:41 -07:00
2018-02-02 11:28:41 -08:00
2018-02-02 11:28:41 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-01-23 13:16:37 -08:00
2018-02-15 14:55:43 -08:00
2017-11-21 14:07:50 +09:00
2018-02-15 15:21:23 -08:00
2018-02-13 10:59:58 -08:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2018-01-24 13:42:23 -08:00
2018-02-13 13:39:11 -08:00
2017-06-24 14:28:41 -07:00
2017-09-06 17:19:54 +09:00
2018-02-13 13:39:03 -08:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-02-02 11:28:41 -08:00
2017-08-22 10:29:03 -07:00
2017-05-29 12:34:43 +09:00
2018-01-22 11:32:51 -08: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
2018-01-16 12:16:54 -08:00
2018-02-15 14:55:47 -08:00
2018-02-15 15:21:23 -08:00
2018-01-22 11:32:51 -08:00
2018-01-22 11:32:51 -08:00
2018-02-15 14:55:43 -08:00
2018-02-27 10:33:58 -08:00
2018-02-15 14:55:47 -08:00
2017-09-29 11:23:43 +09:00
2017-08-26 22:55:04 -07:00
2018-02-13 13:39:04 -08:00
2018-02-13 13:39:04 -08:00
2017-06-24 14:28:41 -07:00
2018-02-13 13:39:04 -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%