Junio C Hamano 96379f043f Merge branch 'en/merge-directory-renames'
"git merge-recursive" backend recently learned a new heuristics to
infer file movement based on how other files in the same directory
moved.  As this is inherently less robust heuristics than the one
based on the content similarity of the file itself (rather than
based on what its neighbours are doing), it sometimes gives an
outcome unexpected by the end users.  This has been toned down to
leave the renamed paths in higher/conflicted stages in the index so
that the user can examine and confirm the result.

* en/merge-directory-renames:
  merge-recursive: switch directory rename detection default
  merge-recursive: give callers of handle_content_merge() access to contents
  merge-recursive: track information associated with directory renames
  t6043: fix copied test description to match its purpose
  merge-recursive: switch from (oid,mode) pairs to a diff_filespec
  merge-recursive: cleanup handle_rename_* function signatures
  merge-recursive: track branch where rename occurred in rename struct
  merge-recursive: remove ren[12]_other fields from rename_conflict_info
  merge-recursive: shrink rename_conflict_info
  merge-recursive: move some struct declarations together
  merge-recursive: use 'ci' for rename_conflict_info variable name
  merge-recursive: rename locals 'o' and 'a' to 'obuf' and 'abuf'
  merge-recursive: rename diff_filespec 'one' to 'o'
  merge-recursive: rename merge_options argument from 'o' to 'opt'
  Use 'unsigned short' for mode, like diff_filespec does
2019-05-09 00:37:22 +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-04-12 13:34:17 +09:00
2019-04-22 11:14:43 +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
2019-02-05 14:26:09 -08:00
2018-11-19 16:24:41 +09:00
2018-08-20 12:41:32 -07:00
2019-04-25 16:41:12 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2019-03-07 09:59:51 +09:00
2019-03-07 11:59:54 +09:00
2019-04-25 16:41:14 +09:00
2018-11-05 13:42:11 +09:00
2018-12-12 17:18:29 +09:00
2019-04-25 16:41:17 +09:00
2019-04-25 16:41:17 +09:00
2019-04-22 11:14:43 +09:00
2019-04-01 11:57:37 +09:00
2018-08-29 13:05:35 -07:00
2019-04-22 11:14:46 +09:00
2019-01-14 12:13:04 -08: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
2018-10-19 13:34:02 +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-11-02 12:14:21 +09:00
2019-04-25 16:41:23 +09:00
2018-12-09 12:37:32 +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
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-02-06 22:05:23 -08:00
2018-08-15 11:52:09 -07: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
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%