Derrick Stolee ce1e4a105b midx: implement midx_repack()
To repack with a non-zero batch-size, first sort all pack-files by
their modified time. Second, walk those pack-files from oldest
to newest, compute their expected size, and add the packs to a list
if they are smaller than the given batch-size. Stop when the total
expected size is at least the batch size.

If the batch size is zero, select all packs in the multi-pack-index.

Finally, collect the objects from the multi-pack-index that are in
the selected packs and send them to 'git pack-objects'. Write a new
multi-pack-index that includes the new pack.

Using a batch size of zero is very similar to a standard 'git repack'
command, except that we do not delete the old packs and instead rely
on the new multi-pack-index to prevent new processes from reading the
old packs. This does not disrupt other Git processes that are currently
reading the old packs based on the old multi-pack-index.

While first designing a 'git multi-pack-index repack' operation, I
started by collecting the batches based on the actual size of the
objects instead of the size of the pack-files. This allows repacking
a large pack-file that has very few referencd objects. However, this
came at a significant cost of parsing pack-files instead of simply
reading the multi-pack-index and getting the file information for
the pack-files. The "expected size" version provides similar
behavior, but could skip a pack-file if the average object size is
much larger than the actual size of the referenced objects, or
can create a large pack if the actual size of the referenced objects
is larger than the expected size.

Signed-off-by: Derrick Stolee <dstolee@microsoft.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-06-11 10:34:40 -07:00
2019-05-19 16:45:31 +09:00
2019-04-01 11:57:39 +09:00
2019-04-01 11:57:39 +09:00
2019-04-16 19:28:11 +09:00
2019-05-14 16:45:01 +09:00
2019-06-11 10:34:40 -07:00
2019-05-30 10:50:45 -07:00
2019-04-12 13:34:17 +09:00
2019-05-09 00:37:27 +09:00
2019-04-12 10:52:35 +09:00
2018-08-20 12:41:32 -07:00
2018-09-12 15:15:34 -07:00
2019-01-02 10:19:05 -08:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2019-05-09 00:37:25 +09:00
2019-05-13 23:50:31 +09:00
2018-08-20 12:41:32 -07:00
2017-12-08 09:16:27 -08:00
2019-05-05 15:20:10 +09:00
2019-05-30 10:50:44 -07:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2019-05-13 23:50:32 +09:00
2019-03-07 09:59:51 +09:00
2019-06-07 09:39:21 -07:00
2019-05-09 00:37:27 +09:00
2019-05-05 15:20:10 +09:00
2019-04-22 11:14:43 +09:00
2017-09-06 17:19:54 +09:00
2018-08-29 13:05:35 -07:00
2019-05-19 16:45:28 +09:00
2019-01-14 12:13:04 -08:00
2019-06-11 10:34:40 -07:00
2019-02-07 13:02:28 -08:00
2018-10-04 11:12:14 -07:00
2019-04-01 11:57:37 +09:00
2019-05-05 15:20:10 +09:00
2018-10-19 13:34:02 +09:00
2019-05-05 15:20:10 +09:00
2019-02-06 22:05:23 -08:00
2019-02-05 14:26:09 -08:00
2018-11-02 12:14:21 +09:00
2018-12-09 12:37:32 +09:00
2019-05-05 15:20:10 +09:00
2018-08-15 15:08:23 -07:00
2019-04-01 11:57:39 +09:00
2019-03-07 11:59:54 +09:00
2019-01-14 12:13:04 -08:00
2019-05-05 15:20:10 +09:00
2018-06-01 15:06:37 +09:00
2019-02-05 14:26:11 -08:00
2019-04-22 11:14:43 +09:00
2019-04-22 11:14:43 +09:00
2018-12-09 12:37:32 +09:00
2019-05-05 15:20:10 +09:00
2019-05-13 23:50:35 +09:00
2019-05-05 15:20:10 +09:00
2019-02-06 22:05:23 -08:00
2018-10-19 13:34:02 +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-.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
No description provided
Readme 614 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%