Junio C Hamano 5de7166d46 apply.c:update_pre_post_images(): the preimage can be truncated
5166714 (apply: Allow blank context lines to match beyond EOF,
2010-03-06) and then later 0c3ef98 (apply: Allow blank *trailing*
context lines to match beyond EOF, 2010-04-08) taught "git apply"
to trim new blank lines at the end in the patch text when matching
the contents being patched and the preimage recorded in the patch,
under --whitespace=fix mode.

When a preimage is modified to match the current contents in
preparation for such a "fixed" patch application, the context lines
in the postimage must be updated to match (otherwise, it would
reintroduce whitespace breakages), and update_pre_post_images()
function is responsible for doing this.  However, this function was
not updated to take into account a case where the removal of
trailing blank lines reduces the number of lines in the preimage,
and triggered an assertion error.

The logic to fix the postimage by copying the corrected context
lines from the preimage was not prepared to handle this case,
either, but it was protected by the assert() and only got exposed
when the assertion is corrected.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-10-12 16:06:49 -07:00
2012-09-14 20:57:23 -07:00
2012-07-01 23:04:09 +01:00
2011-03-17 15:30:49 -07:00
2011-10-21 16:04:32 -07:00
2012-05-03 15:13:31 -07:00
2012-03-26 12:03:40 -07:00
2009-09-13 01:32:26 -07:00
2012-03-07 12:12:59 -08:00
2012-01-08 15:08:03 -08:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-05-07 09:34:27 -07:00
2012-08-23 21:30:51 -07:00
2012-09-14 20:57:23 -07:00
2012-05-03 15:13:31 -07:00
2012-04-06 10:15:11 -07:00
2012-05-03 15:13:31 -07:00
2011-12-19 16:06:41 -08:00
2011-08-20 22:33:57 -07:00
2009-04-22 19:02:12 -07:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2010-01-12 01:06:09 -08:00
2012-01-06 12:44:07 -08:00
2010-04-01 23:58:30 -07:00
2011-08-22 10:07:07 -07:00
2011-11-06 20:31:28 -08:00
2011-12-16 22:33:40 -08:00
2012-04-27 09:26:38 -07:00
2012-08-03 12:11:07 -07:00
2011-12-12 16:09:38 -08:00
2011-11-07 22:12:19 -08:00
2012-05-29 13:09:02 -07:00
2012-04-10 15:55:55 -07:00
2012-09-14 20:57:23 -07:00
2012-06-01 13:28:19 -07:00
2010-05-04 15:38:58 -07:00
2009-11-04 17:58:15 -08:00
2011-12-11 23:16:24 -08:00
2009-08-23 17:11:28 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-12-11 23:16:25 -08:00
2011-10-17 21:37:15 -07:00
2012-05-08 04:57:42 -04: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 (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 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 582 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%