1
0
mirror of https://github.com/git/git.git synced 2025-04-18 22:33:46 +00:00
Jeff King 13494ed14c correct cache_entry allocation
Most cache_entry structs are allocated by using the
cache_entry_size macro, which rounds the size of the struct
up to the nearest multiple of 8 bytes (presumably to avoid
memory fragmentation).

There is one exception: the special "conflict entry" is
allocated with an empty name, and so is explicitly given
just one extra byte to hold the NUL.

However, later code doesn't realize that this particular
struct has been allocated differently, and happily tries
reading and copying it based on the ce_size macro, which
assumes the 8-byte alignment.

This can lead to reading uninitalized data, though since
that data is simply padding, there shouldn't be any problem
as a result. Still, it makes sense to hold the padding
assumption so as not to surprise later maintainers.

This fixes valgrind errors in t1005, t3030, t4002, and
t4114.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2008-11-01 23:46:34 -07:00
2008-07-07 02:17:23 -07:00
2008-07-19 11:25:51 -07:00
2008-06-30 22:45:50 -07:00
2008-07-19 11:17:43 -07:00
2008-07-19 11:17:43 -07:00
2008-10-26 16:19:59 -07:00
2008-07-20 17:53:17 -07:00
2008-07-13 14:12:48 -07:00
2008-09-19 22:05:31 -07:00
2008-07-16 17:22:50 -07:00
2008-08-28 20:50:10 -07:00
2008-07-13 14:12:48 -07:00
2008-03-14 00:16:42 -07:00
2008-08-03 14:14:10 -07:00
2008-08-11 00:53:31 -07:00
2008-08-06 13:50:48 -07:00
2008-09-15 23:11:35 -07:00
2008-07-28 23:26:25 -07:00
2008-07-16 14:03:24 -07:00
2008-07-25 17:09:38 -07:00
2008-03-05 10:32:01 -08:00
2008-08-16 02:32:36 -07:00
2008-08-11 19:24:28 -07:00
2008-07-15 19:09:46 -07:00
2008-08-05 21:21:08 -07:00
2008-07-13 14:12:48 -07:00
2008-07-13 14:12:48 -07:00
2008-07-25 13:56:36 -07:00
2008-07-13 14:12:48 -07:00
2008-09-12 16:18:47 -07:00
2008-07-13 14:12:48 -07:00
2008-08-21 22:18:21 -07:00
2008-07-13 14:12:48 -07:00
2008-07-19 11:28:06 -07:00
2008-08-04 21:52:08 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-10-28 08:57:08 -07:00
2008-07-13 14:12:48 -07:00
2008-06-26 08:47:15 +02:00
2008-08-06 13:50:48 -07:00
2008-08-06 13:50:48 -07:00
2008-07-21 19:11:50 -07:00
2008-07-09 00:19:50 -07:00
2008-09-19 23:15:13 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-08-24 23:28:02 -07:00
2008-10-06 00:37:30 -07:00
2008-07-21 19:11:50 -07:00
2008-07-25 17:09:38 -07:00
2008-07-21 19:11:50 -07:00
2008-07-21 19:11:50 -07:00
2008-03-02 15:11:07 -08:00
2008-11-01 23:46:34 -07:00
2008-07-30 11:42:01 -07:00
2008-07-13 15:15:23 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 864 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%