Nguyễn Thái Ngọc Duy ed7e5fc3a2 repack: add --keep-pack option
We allow to keep existing packs by having companion .keep files. This
is helpful when a pack is permanently kept. In the next patch, git-gc
just wants to keep a pack temporarily, for one pack-objects
run. git-gc can use --keep-pack for this use case.

A note about why the pack_keep field cannot be reused and
pack_keep_in_core has to be added. This is about the case when
--keep-pack is specified together with either --keep-unreachable or
--unpack-unreachable, but --honor-pack-keep is NOT specified.

In this case, we want to exclude objects from the packs specified on
command line, not from ones with .keep files. If only one bit flag is
used, we have to clear pack_keep on pack files with the .keep file.

But we can't make any assumption about unreachable objects in .keep
packs. If "pack_keep" field is false for .keep packs, we could
potentially pull lots of unreachable objects into the new pack, or
unpack them loose. The safer approach is ignore all packs with either
.keep file or --keep-pack.

Signed-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-04-16 13:52:29 +09:00
2018-04-16 13:52:29 +09:00
2017-07-06 18:14:44 -07:00
2018-04-16 13:52:29 +09:00
2018-04-10 08:25:45 +09:00
2017-03-13 15:28:54 -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-04-11 13:09:55 +09:00
2018-02-13 10:17:12 -08:00
2018-02-13 10:17:12 -08:00
2017-10-24 10:19:06 +09:00
2017-01-25 14:42:37 -08:00
2018-02-13 13:39:04 -08:00
2018-03-14 09:23:50 -07:00
2018-03-14 09:23:50 -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
2014-03-31 15:29:27 -07:00
2018-03-06 14:54:07 -08:00
2018-04-10 08:25:45 +09:00
2018-02-15 14:55:43 -08:00
2018-03-14 09:23:50 -07:00
2018-04-11 13:09:55 +09:00
2017-03-31 08:33:56 -07:00
2018-04-10 08:31:17 +09:00
2017-11-21 14:05:30 +09:00
2018-04-11 13:09:55 +09:00
2018-04-11 13:09:55 +09:00
2018-04-11 13:09:57 +09:00
2017-06-24 14:28:41 -07:00
2018-02-22 10:08:05 -08:00
2017-01-30 14:17:00 -08:00
2017-09-06 17:19:54 +09:00
2018-04-16 13:52:29 +09:00
2018-04-11 13:09:55 +09:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-04-11 13:09:55 +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
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-04-11 13:09:55 +09:00
2018-04-10 08:25:45 +09:00
2018-04-10 08:31:17 +09:00
2018-04-10 08:25:45 +09:00
2017-03-31 08:33:56 -07:00
2018-04-10 08:25:45 +09:00
2017-03-31 08:33:56 -07:00
2017-09-29 11:23:43 +09:00
2018-03-06 14:54:07 -08:00
2018-04-11 13:09:55 +09:00
2018-04-11 13:09:55 +09:00
2018-02-22 10:08:05 -08:00
2018-02-22 10:08:05 -08:00
2017-08-26 22:55:04 -07:00
2018-04-11 13:09:55 +09:00
2018-02-13 13:39:04 -08:00
2018-03-29 15:39:59 -07:00
2018-02-22 10:08:05 -08: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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%