Johannes Schindelin 34204c8166 pack-objects (mingw): initialize packing_data mutex in the correct spot
In 9ac3f0e5b3 (pack-objects: fix performance issues on packing large
deltas, 2018-07-22), a mutex was introduced that is used to guard the
call to set the delta size. This commit even added code to initialize
it, but at an incorrect spot: in `init_threaded_search()`, while the
call to `oe_set_delta_size()` (and hence to `packing_data_lock()`) can
happen in the call chain `check_object()` <- `get_object_details()` <-
`prepare_pack()` <- `cmd_pack_objects()`, which is long before the
`prepare_pack()` function calls `ll_find_deltas()` (which initializes
the threaded search).

Another tell-tale that the mutex was initialized in an incorrect spot is
that the function to initialize it lives in builtin/, while the code
that uses the mutex is defined in a libgit.a header file.

Let's use a more appropriate function: `prepare_packing_data()`, which
not only lives in libgit.a, but *has* to be called before the
`packing_data` struct is used that contains that mutex.

This fixes https://github.com/git-for-windows/git/issues/1839.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-10-19 14:28:44 +09:00
2018-08-20 11:33:53 -07:00
2018-09-27 11:52:33 -07:00
2018-08-15 15:08:25 -07:00
2018-08-02 13:54:58 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 11:33:53 -07:00
2018-08-13 14:14:43 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 12:41:32 -07:00
2018-07-26 10:12:51 -07:00
2018-07-18 12:20:28 -07:00
2018-08-23 06:20:58 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-08-02 15:30:42 -07:00
2018-05-08 15:59:17 +09:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-05-08 15:59:17 +09:00
2018-08-02 15:30:43 -07:00
2018-09-27 11:50:45 -07:00
2018-05-08 15:59:34 +09:00
2018-08-20 11:33:50 -07:00
2018-08-01 13:37:18 -07:00
2018-09-27 11:52:33 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 11:33:50 -07:00
2018-08-02 15:30:44 -07:00
2018-08-02 15:30:44 -07:00
2018-07-16 14:27:39 -07:00
2018-04-11 13:09:55 +09:00
2018-05-30 21:51:28 +09:00
2018-08-02 15:30:45 -07:00
2018-08-15 15:08:23 -07:00
2018-06-21 12:22:48 -07:00
2018-06-01 15:06:37 +09:00
2018-07-18 12:20:28 -07:00
2018-08-15 15:08:25 -07:00
2018-08-20 11:33:53 -07:00
2018-08-15 15:08:23 -07:00
2018-09-27 11:52:33 -07:00
2018-08-20 11:33:50 -07:00
2018-08-15 15:08:23 -07:00
2018-08-20 12:41:32 -07:00
2018-03-15 12:01:08 -07:00
2018-08-20 11:33:53 -07:00
2018-06-01 15:06:37 +09:00
2018-08-15 15:08:25 -07:00
2018-09-27 11:50:45 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-08-02 15:30:39 -07:00
2018-08-15 11:52:09 -07:00
2018-05-30 21:51:28 +09:00
2018-08-15 15:08:25 -07:00
2018-08-20 12:41:32 -07:00
2018-07-18 12:20:28 -07: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.

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
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 734 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%