Junio C Hamano 8061ae8b46 Merge branch 'jk/commit-buffer-length'
Move "commit->buffer" out of the in-core commit object and keep
track of their lengths.  Use this to optimize the code paths to
validate GPG signatures in commit objects.

* jk/commit-buffer-length:
  reuse cached commit buffer when parsing signatures
  commit: record buffer length in cache
  commit: convert commit->buffer to a slab
  commit-slab: provide a static initializer
  use get_commit_buffer everywhere
  convert logmsg_reencode to get_commit_buffer
  use get_commit_buffer to avoid duplicate code
  use get_cached_commit_buffer where appropriate
  provide helpers to access the commit buffer
  provide a helper to set the commit buffer
  provide a helper to free commit buffer
  sequencer: use logmsg_reencode in get_message
  logmsg_reencode: return const buffer
  do not create "struct commit" with xcalloc
  commit: push commit_index update into alloc_commit_node
  alloc: include any-object allocations in alloc_report
  replace dangerous uses of strbuf_attach
  commit_tree: take a pointer/len pair rather than a const strbuf
2014-07-02 12:53:02 -07:00
2014-02-27 14:01:48 -08:00
2014-06-25 12:23:56 -07:00
2014-06-25 12:32:58 -07:00
2014-06-26 13:44:11 -07:00
2014-04-08 12:00:28 -07:00
2014-04-22 12:49:07 -07:00
2014-06-06 11:02:59 -07:00
2014-05-17 19:08:59 +02:00
2014-07-02 12:52:46 -07:00
2014-01-10 10:32:18 -08:00
2014-05-15 09:49:12 -07:00
2014-05-15 09:49:12 -07:00
2012-10-29 03:08:30 -04:00
2013-06-10 10:55:42 -07:00
2014-05-15 09:49:10 -07:00
2014-06-03 12:06:40 -07:00
2014-05-15 09:49:10 -07:00
2013-12-09 14:54:48 -08:00
2014-01-17 12:21:20 -08:00
2013-07-22 16:06:49 -07:00
2014-01-10 10:33:09 -08:00
2014-01-10 10:33:09 -08:00
2014-06-16 10:07:15 -07:00
2014-03-31 15:29:27 -07:00
2014-06-03 12:06:40 -07:00
2013-07-19 09:26:15 -07:00
2014-01-17 12:21:20 -08:00
2014-06-13 12:09:38 -07:00
2014-04-08 12:00:28 -07:00
2014-06-12 12:22:38 -07:00
2014-06-25 12:21:11 -07:00
2014-06-25 12:22:00 -07:00
2014-06-03 12:06:39 -07:00
2013-05-10 10:27:31 -07:00
2013-05-08 15:31:54 -07:00
2013-04-11 17:39:05 -07:00
2013-07-22 16:06:49 -07:00
2014-04-08 12:00:33 -07:00
2014-05-27 14:02:45 -07:00
2013-07-29 12:32:25 -07:00
2014-06-13 12:09:38 -07:00
2014-06-06 11:17:00 -07:00
2014-04-08 12:00:17 -07:00
2014-03-31 15:29:27 -07:00
2013-07-30 08:13:38 -07:00
2013-07-30 08:13:38 -07:00
2013-02-05 16:13:32 -08:00
2014-06-16 12:17:58 -07:00
2014-06-25 12:21:11 -07:00
2014-06-20 13:12:14 -07:00
2013-07-15 10:56:07 -07:00
2014-04-08 12:00:33 -07:00
2014-01-17 12:21:20 -08:00
2014-05-28 15:45:57 -07:00
2014-06-16 12:18:36 -07:00
2014-06-16 12:18:36 -07:00
2014-02-27 14:01:09 -08:00
2014-03-31 15:29:27 -07:00
2013-09-17 11:37:33 -07:00
2013-09-17 11:37:33 -07:00
2014-02-27 14:04:05 -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 version 2 (some parts of it are under different licenses,
compatible with the GPLv2). It was originally written by Linus
Torvalds with help of a group of hackers around the net.

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://news.gmane.org/gmane.comp.version-control.git/,
http://marc.info/?l=git and other archival sites.

The maintainer frequently sends the "What's cooking" reports that
list the current status of various development topics to the mailing
list.  The discussion following them 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%