1
0
mirror of https://github.com/git/git.git synced 2025-04-12 02:45:22 +00:00
Jeff King 27b5c1a065 provide an initializer for "struct object_info"
An all-zero initializer is fine for this struct, but because
the first element is a pointer, call sites need to know to
use "NULL" instead of "0". Otherwise some static checkers
like "sparse" will complain; see d099b71 (Fix some sparse
warnings, 2013-07-18) for example.  So let's provide an
initializer to make this easier to get right.

But let's also comment that memset() to zero is explicitly
OK[1]. One of the callers embeds object_info in another
struct which is initialized via memset (expand_data in
builtin/cat-file.c). Since our subset of C doesn't allow
assignment from a compound literal, handling this in any
other way is awkward, so we'd like to keep the ability to
initialize by memset(). By documenting this property, it
should make anybody who wants to change the initializer
think twice before doing so.

There's one other caller of interest. In parse_sha1_header(),
we did not initialize the struct fully in the first place.
This turned out not to be a bug because the sub-function it
calls does not look at any other fields except the ones we
did initialize. But that assumption might not hold in the
future, so it's a dangerous construct. This patch switches
it to initializing the whole struct, which protects us
against unexpected reads of the other fields.

[1] Obviously using memset() to initialize a pointer
    violates the C standard, but we long ago decided that it
    was an acceptable tradeoff in the real world.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-08-11 10:42:23 -07:00
2016-05-10 11:19:07 -07:00
2016-07-19 13:22:19 -07:00
2016-07-19 13:22:16 -07:00
2016-07-13 11:24:10 -07:00
2016-05-09 12:29:08 -07:00
2016-06-21 11:18:17 -07:00
2016-07-19 13:22:22 -07:00
2016-05-09 12:29:08 -07:00
2016-07-11 10:31:05 -07:00
2016-07-19 13:22:16 -07:00
2016-07-19 13:22:22 -07:00
2016-07-19 13:22:22 -07:00
2016-07-06 13:38:11 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-07-19 13:22:19 -07:00
2016-07-19 13:22:16 -07:00
2016-05-23 14:54:29 -07:00
2016-05-23 14:54:29 -07:00
2016-05-09 12:29:08 -07:00
2016-05-09 12:29:08 -07:00
2016-07-19 13:22:19 -07:00
2016-05-17 14:38:34 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-07-19 13:22:24 -07:00
2016-07-15 10:48:16 -07:00
2016-07-01 15:09:10 -07:00
2016-07-19 13:22:15 -07:00
2016-07-19 13:22:17 -07:00
2016-06-28 11:39:02 -07:00
2016-07-06 13:38:06 -07:00
2016-07-06 13:38:06 -07:00
2016-07-19 13:22:19 -07:00
2016-07-19 13:22:16 -07:00
2016-05-17 14:38:32 -07:00
2016-05-17 14:38:28 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-07-19 13:22:16 -07:00
2016-07-29 11:05:06 -07:00
2016-05-26 13:17:21 -07:00
2016-07-19 13:22:17 -07:00
2016-07-19 13:22:17 -07:00
2016-05-09 12:29:08 -07:00
2016-07-15 10:48:16 -07:00
2016-05-23 14:54:38 -07:00
2016-07-13 11:24:10 -07:00
2016-05-09 12:29:08 -07:00
2016-05-06 14:45:44 -07:00
2016-07-01 15:09:10 -07:00
2016-07-19 13:22:16 -07:00
2016-07-19 13:22:16 -07:00
2016-07-19 13:22:19 -07:00
2016-07-19 13:22:23 -07:00
2016-07-19 13:22:16 -07:00

Git - fast, scalable, distributed revision control system

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.

Many Git online resources are accessible from http://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.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).

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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
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 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%