Junio C Hamano ac7f0f436e merge-recursive: do not barf on "to be removed" entries.
When update-trees::threeway_merge() decides that a path that
exists in the current index (and HEAD) is to be removed, it
leaves a stage 0 entry whose mode bits are set to 0.  The code
mistook it as "this stage wants the blob here", and proceeded
to call update_file_flags() which ended up trying to put the
mode=0 entry in the index, got very confused, and ended up
barfing with "do not know what to do with 000000".

Since threeway_merge() does not handle case #10 (one side
removes while the other side does not do anything), this is not
a problem while we refuse to merge branches that have D/F
conflicts, but when we start resolving them, we would need to be
able to remove cache entries, and at that point it starts to
matter.

Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-04-10 12:55:51 -07:00
2007-04-05 16:34:51 -07:00
2007-04-05 16:34:51 -07:00
2007-02-03 21:49:54 -08:00
2007-04-10 12:55:51 -07:00
2007-04-07 02:29:40 -07:00
2007-04-07 02:26:24 -07:00
2007-04-07 02:26:24 -07:00
2007-02-27 22:15:42 -08:00
2007-03-17 00:34:19 -07:00
2007-04-07 02:26:24 -07:00
2007-03-20 22:17:47 -07:00
2007-04-05 16:34:51 -07:00
2007-02-24 01:42:06 -08:00
2007-03-17 00:34:19 -07:00
2006-05-01 22:29:16 -07:00
2007-04-07 02:29:40 -07:00
2007-03-02 00:37:12 -08:00
2007-03-27 13:00:13 -07:00
2007-02-14 11:19:28 -08:00
2005-12-27 10:49:25 -08:00
2005-08-09 22:28:19 -07:00
2005-10-14 17:17:27 -07:00
2006-05-15 12:32:13 -07:00
2007-03-14 16:21:19 -07:00
2007-03-14 16:21:19 -07:00
2006-03-05 02:47:29 -08:00
2007-02-28 14:18:57 -08:00
2007-04-08 23:27:22 -07:00
2006-02-06 21:43:27 -08:00
2007-02-03 21:49:54 -08:00
2007-04-07 02:29:40 -07:00
2005-09-07 17:45:20 -07:00
2007-01-18 14:22:24 -08:00
2007-01-30 21:03:11 -08:00
2007-04-03 22:47:01 -07:00
2007-04-05 14:10:10 -07:00
2006-09-27 23:59:09 -07:00
2007-03-27 16:57:57 -07:00
2007-03-07 10:47:10 -08:00
2007-03-07 10:47:10 -08:00
2007-04-03 23:44:32 -07:00
2006-06-26 14:58:41 -07:00
2007-04-07 02:29:40 -07:00
2007-04-07 02:29:40 -07:00
2007-03-19 02:48:37 -07:00
2007-02-27 01:34:21 -08:00
2007-03-07 10:47:10 -08:00
2007-02-08 17:48:22 -08:00
2007-02-03 11:57:18 -08:00
2007-03-12 23:40:18 -07:00
2007-03-10 22:07:26 -08:00
2006-10-20 16:50:36 -07:00
2007-02-27 01:34:21 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2007-03-03 19:47:46 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 606 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%