Elijah Newren 52396e1d3d merge-recursive: set paths correctly when three-way merging content
merge_3way() has code to mark different sides of the conflict with info
about where the content comes from.  If the names of the files involved
match, it simply uses the branch name.  If the names of the files do not
match, it uses branchname:filename.  Unfortunately, merge_content()
previously always called it with one.path = a.path = b.path.  Granted,
it didn't have other path information available to it for years, but
that was corrected by passing rename_conflict_info in commit
3c217c077a ("merge-recursive: Provide more info in conflict markers
with file renames", 2011-08-11).  In that commit, instead of just fixing
the bug with the pathnames, it created fake branch names incorporating
both the branch name and file name.

This "fake branch" workaround was extended further when I pulled that
logic out into a special function in commit dac4741554
("merge-recursive: Create function for merging with branchname:file
markers", 2011-08-11), and a number of other sites outside of
merge_content() have been added which call into that.  However, this
Rube-Goldberg-esque setup is not merely duplicate code and unnecessary
work, it also risked having other callsites invoke it in a way that
would result in markers of the form branchname:filename:filename (i.e.
with the filename repeated).

Fix this whole mess by:
  - setting one.path, a.path, and b.path appropriately
  - calling merge_file_1() directly
  - deleting the merge_file_special_markers() workaround wrapper

Signed-off-by: Elijah Newren <newren@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-09-20 12:33:57 -07:00
2018-08-02 13:54:58 -07:00
2018-09-17 13:54:00 -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-08-29 11:32:49 -07:00
2018-08-29 11:32:49 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:57 -07:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-09-17 13:53:52 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:54 -07:00
2018-05-08 15:59:17 +09:00
2018-08-20 12:41:32 -07:00
2018-08-29 11:32:49 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-08-16 10:51:17 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:54 -07:00
2018-08-20 12:41:32 -07:00
2018-09-17 13:53:57 -07:00
2018-05-08 15:59:17 +09:00
2018-09-17 13:53:57 -07:00
2018-08-02 15:30:43 -07:00
2018-08-02 15:30:42 -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-17 14:16:29 -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-09-17 13:53:57 -07:00
2018-08-29 11:32:49 -07:00
2018-05-30 21:51:28 +09:00
2018-09-17 13:53:57 -07:00
2018-08-29 13:05:35 -07:00
2018-08-02 15:30:45 -07:00
2018-08-20 15:31:40 -07:00
2018-08-20 15:31:40 -07:00
2018-09-17 13:53:57 -07:00
2018-08-29 11:32:49 -07:00
2018-08-20 15:31:40 -07:00
2018-08-29 11:32:49 -07:00
2018-09-17 13:53:52 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:55 -07:00
2018-09-17 13:53:57 -07:00
2018-08-20 15:31:40 -07:00
2018-06-01 15:06:37 +09:00
2018-07-18 12:20:28 -07:00
2018-09-17 13:53:54 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:54 -07:00
2018-08-15 15:08:23 -07:00
2018-08-29 11:32:49 -07:00
2018-09-17 14:16:29 -07:00
2018-08-20 11:33:50 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:52 -07:00
2018-08-15 15:08:23 -07:00
2018-09-17 13:53:51 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:54 -07:00
2018-08-20 15:31:40 -07:00
2018-09-17 13:53:57 -07:00
2018-07-20 15:38:54 -07:00
2018-06-01 15:06:37 +09:00
2018-08-15 15:08:25 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:54 -07:00
2018-08-29 11:32:49 -07:00
2018-08-02 15:30:39 -07:00
2018-09-17 13:53:57 -07:00
2018-09-17 13:53:52 -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
2018-08-29 11:32:49 -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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%