Jeff King 63433a4706 merge: turn on rewrite detection
We currently don't do break-detection at all in
merge-recursive. But there are some cases where it would
provide a more useful merge result.

For example, consider this case (which is the basis for the
new tests in t6039):

  1. You rename a header file foo.h to bar.h. You install a
     new foo.h that includes bar.h (for compatibility).

  2. Another branch makes changes to foo.h.

When you merge, you want the changes the other branch made
to foo.h to migrate to the rename destination, bar.h, just
as you would if you hadn't installed that compatibility
header.

Similarly, you want the compatibility header left untouched.
The other side's changes all ended up in bar.h, so there is
no reason to conflict with the new content in foo.h.

This patch turns on break detection for merge-recursive. In
addition to new tests in t6039, it makes a similar test in
t3030 pass.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-03-25 11:12:57 -07:00
2011-01-08 23:48:47 -08:00
2011-03-25 11:12:57 -07:00
2010-12-28 11:26:55 -08:00
2010-12-08 11:24:14 -08:00
2011-02-06 22:50:26 -08:00
2011-01-19 08:27:22 -08:00
2011-01-05 13:30:29 -08:00
2011-01-27 10:27:49 -08:00
2011-02-11 14:39:55 -08:00
2010-12-28 11:26:55 -08:00
2010-06-30 15:49:18 -07:00
2010-08-22 20:18:37 -07:00
2010-11-26 14:50:46 -08:00
2010-12-20 10:28:19 -08:00
2010-08-09 11:35:46 -07:00
2010-11-24 15:13:58 -08:00
2010-08-26 09:20:03 -07:00
2010-10-13 19:11:26 -07:00
2011-03-20 22:11:15 -07:00
2010-12-08 11:24:12 -08:00
2010-12-08 11:24:12 -08:00
2010-09-06 00:12:04 -07:00
2011-02-07 15:15:17 -08:00
2010-12-03 16:10:34 -08:00
2010-10-26 21:40:54 -07:00
2010-09-27 10:42:11 -07:00
2011-02-07 15:04:42 -08:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:38 -07:00
2010-10-13 16:08:58 -07:00
2010-10-26 21:37:49 -07:00
2010-08-26 16:42:59 -07:00
2011-01-24 10:54:12 -08:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, 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

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.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.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).

Many Git online resources are accessible from http://git-scm.com/
including full documentation and Git related tools.

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. 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
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
No description provided
Readme 678 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%