Matheus Tavares c441ea4edc grep: allow submodule functions to run in parallel
Now that object reading operations are internally protected, the
submodule initialization functions at builtin/grep.c:grep_submodule()
are very close to being thread-safe. Let's take a look at each call and
remove from the critical section what we can, for better performance:

- submodule_from_path() and is_submodule_active() cannot be called in
  parallel yet only because they call repo_read_gitmodules() which
  contains, in its call stack, operations that would otherwise be in
  race condition with object reading (for example parse_object() and
  is_promisor_remote()). However, they only call repo_read_gitmodules()
  if it wasn't read before. So let's pre-read it before firing the
  threads and allow these two functions to safely be called in
  parallel.

- repo_submodule_init() is already thread-safe, so remove it from the
  critical section without other necessary changes.

- The repo_read_gitmodules(&subrepo) call at grep_submodule() is safe as
  no other thread is performing object reading operations in the subrepo
  yet. However, threads might be working in the superproject, and this
  function calls add_to_alternates_memory() internally, which is racy
  with object readings in the superproject. So it must be kept
  protected for now. Let's add a "NEEDSWORK" to it, informing why it
  cannot be removed from the critical section yet.

- Finally, add_to_alternates_memory() must be kept protected for the
  same reason as the item above.

Signed-off-by: Matheus Tavares <matheus.bernardino@usp.br>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-01-17 13:52:14 -08:00
2019-12-06 15:09:21 -08:00
2019-12-01 09:04:35 -08:00
2019-09-28 14:04:16 +09:00
2019-11-20 13:29:02 +09:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2019-10-15 13:48:02 +09:00
2020-01-06 14:17:51 -08:00
2019-12-25 11:21:58 -08:00
2019-11-10 16:00:54 +09:00
2019-11-22 16:11:44 +09:00
2019-12-06 16:31:39 +01:00
2019-12-01 09:04:36 -08:00
2019-12-06 16:31:39 +01:00
2019-11-13 11:48:47 +09:00
2019-12-01 09:04:36 -08:00
2019-11-10 16:00:54 +09:00
2019-12-05 12:52:43 -08:00
2019-12-16 13:08:39 -08:00
2019-10-15 13:48:02 +09:00
2019-12-25 11:22:02 -08:00
2019-12-25 11:21:58 -08:00
2019-12-25 11:21:58 -08:00
2019-12-06 16:31:39 +01:00
2019-12-09 22:17:55 -08:00
2019-12-09 22:17:55 -08:00
2020-01-02 12:38:29 -08:00
2020-01-13 10:16:43 -08:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2019-12-01 09:04:35 -08:00
2019-11-13 10:09:10 +09:00
2019-12-01 09:04:33 -08:00
2019-11-18 15:21:28 +09:00
2019-12-25 11:22:01 -08:00
2019-10-23 12:05:05 +09:00
2019-12-01 09:04:35 -08:00
2019-12-09 22:17:55 -08:00
2019-12-16 13:08:39 -08:00
2019-12-02 08:48:56 -08:00
2019-12-10 13:11:43 -08:00
2019-11-27 10:57:10 +09:00
2019-10-15 13:48:02 +09:00
2019-10-15 13:48:02 +09:00
2019-11-18 15:21:28 +09:00
2019-12-06 16:31:40 +01:00
2019-11-10 16:00:54 +09:00
2019-09-30 13:19:26 +09:00
2019-11-13 10:09:10 +09:00
2019-10-11 14:24:48 +09:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:30 +01:00
2019-12-06 16:31:30 +01:00
2019-11-18 15:21:29 +09:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:39 +01:00
2019-11-18 15:21:29 +09:00
2019-11-10 16:00:54 +09:00
2019-12-25 11:21:59 -08:00
2019-10-09 14:01:00 +09:00
2019-10-11 14:24:46 +09: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). 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://lore.kernel.org/git/, http://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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%