Elijah Newren 2dd6f8aa84 merge-recursive: introduce new functions to handle rename logic
The amount of logic in merge_trees() relative to renames was just a few
lines, but split it out into new handle_renames() and cleanup_renames()
functions to prepare for additional logic to be added to each.  No code or
logic changes, just a new place to put stuff for when the rename detection
gains additional checks.

Note that process_renames() records pointers to various information (such
as diff_filepairs) into rename_conflict_info structs.  Even though the
rename string_lists are not directly used once handle_renames() completes,
we should not immediately free the lists at the end of that function
because they store the information referenced in the rename_conflict_info,
which is used later in process_entry().  Thus the reason for a separate
cleanup_renames().

Reviewed-by: Stefan Beller <sbeller@google.com>
Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-02-14 13:02:52 -08:00
2017-11-21 14:07:50 +09:00
2018-01-17 13:06:51 -08:00
2018-01-15 07:47:30 +01:00
2018-01-10 14:01:25 -08:00
2017-11-15 12:14:28 +09:00
2017-12-27 11:16:25 -08:00
2017-12-27 11:16:25 -08:00
2017-11-06 13:11:21 +09:00
2017-12-04 09:38:30 -08:00
2017-10-24 10:19:06 +09:00
2017-11-08 11:34:00 +09:00
2017-12-12 10:39:43 -08:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2017-12-13 13:28:54 -08:00
2017-12-28 14:08:46 -08:00
2017-11-28 10:40:04 +09:00
2017-12-27 11:16:21 -08:00
2017-12-27 11:16:21 -08:00
2017-11-21 14:07:50 +09:00
2018-01-17 13:06:51 -08:00
2017-11-28 13:41:50 +09:00
2017-12-13 13:28:54 -08:00
2017-11-21 14:05:30 +09:00
2017-11-01 10:35:39 +09:00
2017-12-28 14:08:50 -08:00
2018-01-09 14:32:53 -08:00
2017-11-09 14:31:27 +09:00
2017-11-22 14:11:56 +09:00
2017-10-28 10:18:40 +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
2017-11-27 11:06:37 +09:00
2017-12-06 09:10:35 -08:00
2017-12-28 14:08:50 -08:00
2017-12-28 14:08:50 -08:00
2017-12-19 11:33:58 -08:00
2017-11-21 14:07:50 +09:00
2017-12-06 09:23:44 -08:00
2017-11-06 14:24:27 +09: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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%