René Scharfe 462749b728 utf8.c: speculatively assume utf-8 in strbuf_add_wrapped_text()
is_utf8() works by calling utf8_width() for each character at the
supplied location.  In strbuf_add_wrapped_text(), we do that anyway
while wrapping the lines.  So instead of checking the encoding
beforehand, optimistically assume that it's utf-8 and wrap along
until an invalid character is hit, and when that happens start over.

This pays off if the text consists only of valid utf-8 characters.
The following command was run against the Linux kernel repo with
git 1.7.0:

	$ time git log --format='%b' v2.6.32 >/dev/null

	real	0m2.679s
	user	0m2.580s
	sys	0m0.100s

	$ time git log --format='%w(60,4,8)%b' >/dev/null

	real	0m4.342s
	user	0m4.230s
	sys	0m0.110s

And with this patch series:

	$ time git log --format='%w(60,4,8)%b' >/dev/null

	real	0m3.741s
	user	0m3.630s
	sys	0m0.110s

So the cost of wrapping is reduced to 70% in this case.

Signed-off-by: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-02-20 09:22:44 -08:00
2009-11-20 23:48:11 -08:00
2009-11-20 23:48:52 -08:00
2009-10-27 14:55:37 -07:00
2009-09-14 02:23:36 -07:00
2008-07-19 11:17:43 -07:00
2009-06-30 16:12:24 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2009-10-30 20:18:31 -07:00
2009-10-30 15:18:11 -07:00
2008-08-28 20:50:10 -07:00
2009-03-14 13:36:34 -07:00
2009-11-20 23:51:23 -08:00
2009-08-05 12:39:33 -07:00
2009-08-07 22:35:17 -07:00
2009-11-20 23:53:55 -08:00
2009-02-13 17:27:58 -08:00
2009-07-22 21:56:46 -07:00
2009-11-20 23:53:55 -08:00
2009-11-20 23:51:23 -08:00
2009-10-19 18:59:42 -07:00
2009-10-30 19:20:53 -07:00
2009-09-13 01:32:26 -07:00
2008-10-10 08:39:20 -07:00
2009-05-01 16:07:29 -07:00
2009-10-03 06:04:38 -04:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2008-11-02 16:36:40 -08:00
2009-10-19 18:59:42 -07:00
2009-04-22 19:02:12 -07:00
2009-11-15 16:41:02 -08:00
2008-07-13 14:12:48 -07:00
2009-11-20 23:48:52 -08:00
2009-11-16 00:05:12 -08:00
2008-09-25 08:00:28 -07:00
2009-07-02 21:36:42 -07:00
2009-09-13 01:30:53 -07:00
2009-09-18 20:00:42 -07:00
2008-09-07 23:52:16 -07:00
2009-11-20 23:51:23 -08:00
2009-11-04 17:58:15 -08:00
2009-11-04 17:58:15 -08:00
2009-11-13 12:16:30 -08:00
2009-11-20 23:44:52 -08:00
2009-04-22 19:02:12 -07:00
2009-11-20 23:53:55 -08:00
2008-10-25 12:09:31 -07:00
2009-08-21 18:47:53 -07:00
2009-08-21 18:47:53 -07:00
2009-11-20 23:53:55 -08:00
2009-11-16 00:05:12 -08:00
2009-11-20 23:51:23 -08:00
2009-06-20 21:47:27 -07:00
2009-02-14 21:27:35 -08:00
2009-11-04 17:58:15 -08:00
2008-07-21 19:11:50 -07:00
2009-11-04 17:58:15 -08:00
2008-03-02 15:11:07 -08:00
2009-01-17 18:30:41 -08:00
2009-08-30 22:04:46 -07:00
2009-11-20 23:51:23 -08:00
2009-04-20 13:44:14 -07:00
2009-11-20 23:51:23 -08:00
2009-11-22 16:14:48 -08:00
2010-02-20 09:18:04 -08:00
2009-11-13 12:20:47 -08: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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%