Thomas Rast 09457d2867 log -L: do not free parents lists we might need again
The parent rewriting code of 'git log -L' was too aggressive in
freeing memory: assign_range_to_parent() will free the commit->parents
field when it sees that a parent cannot pass off any blame (is a root
commit in rewritten history).

Its caller assign_parents_range() however will, upon finding the first
parent that takes *full* blame for all ranges, rewind and reinstate
all previous parents' line ranges and parent lists.  This resurrects
pointers to ranges that were freed in assign_range_to_parent() under
some circumstances.

Furthermore, we must not empty the parent lists either: the same
rewind/reinstate code relies on them.

Do both only if the commit was an ordinary (not merge or root) commit,
in which case the merge code-path discussed here is never taken.

Reported-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Thomas Rast <trast@student.ethz.ch>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-09-12 10:27:21 -07:00
2010-08-12 19:10:02 -07:00
2010-06-21 06:02:45 -07:00
2010-06-13 20:02:50 -07:00
2010-02-07 15:52:28 -08:00
2010-07-15 12:04:32 -07:00
2010-06-18 08:49:03 -07:00
2010-08-22 09:39:16 -07:00
2010-05-31 17:36:27 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-06-21 06:02:49 -07:00
2010-06-27 12:07:55 -07:00
2009-11-23 22:30:08 -08:00
2010-06-27 12:07:55 -07:00
2010-04-01 23:53:54 -07:00
2010-06-30 11:55:40 -07:00
2010-06-21 06:02:49 -07:00
2010-06-21 06:02:44 -07:00
2010-06-21 06:02:44 -07:00
2010-06-21 06:02:44 -07:00
2010-06-21 06:02:49 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-08-12 14:18:50 -07:00
2010-08-12 14:18:50 -07:00
2010-05-07 09:34:27 -07:00
2010-01-20 14:37:25 -08:00
2010-06-21 06:02:49 -07:00
2010-06-21 06:02:44 -07:00
2010-05-28 15:08:27 -07:00
2010-06-21 06:02:49 -07:00
2010-02-11 23:06:32 -08:00
2009-12-13 23:40:24 -08:00
2010-05-25 10:49:54 -07:00
2010-06-13 20:02:50 -07:00
2010-07-21 12:55:50 -07:00
2010-07-15 12:09:14 -07:00
2010-06-30 15:49:18 -07:00
2010-06-21 06:02:44 -07:00
2010-01-21 20:03:45 -08:00
2010-06-21 06:02:44 -07:00
2009-04-22 19:02:12 -07:00
2010-01-12 01:06:09 -08:00
2010-06-21 06:02:44 -07:00
2010-04-01 23:58:30 -07:00
2010-04-01 23:58:30 -07:00
2010-06-25 11:45:27 -07:00
2010-04-19 22:16:35 -07:00
2010-01-17 22:49:36 -08:00
2010-06-22 09:45:22 -07:00
2010-07-07 11:18:26 -07:00
2010-01-20 14:46:35 -08:00
2010-08-12 19:10:02 -07:00
2010-08-12 19:10:02 -07:00
2010-06-21 06:02:45 -07:00
2010-07-20 11:29:30 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-01-20 20:28:50 -08:00
2010-01-17 22:49:36 -08:00
2010-04-12 21:45:17 -07:00
2010-04-12 21:45:17 -07:00
2009-01-17 18:30:41 -08:00
2009-08-23 17:11:28 -07:00
2009-04-20 13:44:14 -07:00
2010-01-24 17:35:58 -08:00
2010-05-24 16:48:32 -07:00
2010-06-13 11:22:05 -07:00
2010-04-02 00:05:31 -07:00
2009-07-22 21:57:41 -07: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 557 MiB
Languages
C 50.4%
Shell 38.7%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.4%