Junio C Hamano a20d3c0de1 diff --stat: move the "total count" logic to the last loop
The diffstat generation logic, with --stat-count limit, is
implemented as three loops.

 - The first counts the width necessary to show stats up to
   specified number of entries, and notes up to how many entries in
   the data we need to iterate to show the graph;

 - The second iterates that many times to draw the graph, adjusts
   the number of "total modified files", and counts the total
   added/deleted lines for the part that was shown in the graph;

 - The third iterates over the remainder and only does the part to
   count "total added/deleted lines" and to adjust "total modified
   files" without drawing anything.

Move the logic to count added/deleted lines and modified files from
the second loop to the third loop.

This incidentally fixes a bug.  The third loop was not filtering
binary changes (counted in bytes) from the total added/deleted as it
should.  The second loop implemented this correctly, so if a binary
change appeared earlier than the --stat-count cutoff, the code
counted number of added/deleted lines correctly, but if it appeared
beyond the cutoff, the number of lines would have mixed with the
byte count in the buggy third loop.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-11-27 13:21:15 -08:00
2012-10-13 23:05:54 -07:00
2012-10-17 10:39:44 -07:00
2012-07-13 15:37:04 -07:00
2012-09-17 15:53:31 -07:00
2012-09-03 16:24:23 -07:00
2012-09-02 21:10:01 -07:00
2012-08-21 14:46:11 -07:00
2012-03-07 12:12:59 -08:00
2012-08-15 11:01:55 -07:00
2012-09-11 11:36:05 -07:00
2012-09-07 11:09:04 -07:00
2012-09-19 17:31:25 -07:00
2012-08-21 15:27:15 -07:00
2012-08-23 21:30:51 -07:00
2012-10-17 10:39:44 -07:00
2012-06-25 11:55:51 -07:00
2012-04-06 10:15:11 -07:00
2012-07-25 11:08:59 -07:00
2012-05-03 15:13:31 -07:00
2012-09-11 11:36:05 -07:00
2012-09-11 11:23:54 -07:00
2012-04-27 09:26:38 -07:00
2012-08-03 12:11:07 -07:00
2012-05-29 13:09:02 -07:00
2012-04-10 15:55:55 -07:00
2012-10-17 10:36:42 -07:00
2012-09-18 14:37:46 -07:00
2012-09-18 14:37:46 -07:00
2012-09-10 15:31:06 -07:00
2012-07-22 12:55:07 -07:00
2012-09-16 21:54:47 -07:00
2012-07-08 22:03:46 -07:00
2012-07-08 22:03:46 -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 (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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%