Linus Torvalds 2af202be3d Fix various sparse warnings in the git source code
There are a few remaining ones, but this fixes the trivial ones. It boils
down to two main issues that sparse complains about:

 - warning: Using plain integer as NULL pointer

   Sparse doesn't like you using '0' instead of 'NULL'. For various good
   reasons, not the least of which is just the visual confusion. A NULL
   pointer is not an integer, and that whole "0 works as NULL" is a
   historical accident and not very pretty.

   A few of these remain: zlib is a total mess, and Z_NULL is just a 0.
   I didn't touch those.

 - warning: symbol 'xyz' was not declared. Should it be static?

   Sparse wants to see declarations for any functions you export. A lack
   of a declaration tends to mean that you should either add one, or you
   should mark the function 'static' to show that it's in file scope.

   A few of these remain: I only did the ones that should obviously just
   be made static.

That 'wt_status_submodule_summary' one is debatable. It has a few related
flags (like 'wt_status_use_color') which _are_ declared, and are used by
builtin-commit.c. So maybe we'd like to export it at some point, but it's
not declared now, and not used outside of that file, so 'static' it is in
this patch.

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2009-06-20 21:52:55 -07:00
2009-06-13 12:50:42 -07:00
2009-05-01 22:11:57 -07:00
2009-05-23 01:44:06 -07:00
2009-06-20 21:51:13 -07:00
2009-05-23 01:39:15 -07:00
2009-04-17 21:42:12 -07:00
2009-05-25 01:07:25 -07:00
2009-06-18 09:22:46 -07:00
2009-04-17 21:05:49 -07:00
2009-06-18 09:22:46 -07:00
2009-06-03 00:49:40 -07:00
2009-03-14 13:36:34 -07:00
2009-05-31 16:57:42 -07:00
2009-04-18 14:45:59 -07:00
2009-05-10 12:41:35 -07:00
2009-02-13 17:27:58 -08:00
2009-05-05 22:49:43 -07:00
2009-06-13 12:48:34 -07:00
2009-05-01 16:07:29 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2009-06-20 21:47:30 -07:00
2009-06-09 00:29:36 -07:00
2009-04-22 19:02:12 -07:00
2009-06-13 12:48:34 -07:00
2009-06-20 21:47:13 -07:00
2009-06-03 22:47:48 -07:00
2009-05-10 12:41:35 -07:00
2009-06-03 11:32:29 -07:00
2009-05-09 00:29:56 -07:00
2009-06-18 10:39:17 -07:00
2009-04-22 19:02:12 -07:00
2009-05-13 20:55:49 -07:00
2009-06-13 12:50:42 -07:00
2009-05-20 00:02:24 -07:00
2009-05-25 19:44:52 -07:00
2009-05-13 20:55:48 -07:00
2009-05-25 19:20:39 -07:00
2009-06-20 21:47:27 -07:00
2009-02-14 21:27:35 -08:00
2009-04-22 19:02:12 -07:00
2009-06-07 16:23:04 -07:00
2009-01-17 18:30:41 -08:00
2009-06-13 12:53:19 -07:00
2009-04-22 19:02:12 -07:00
2009-04-20 13:44:14 -07:00
2009-02-04 16:30:43 -08:00
2009-02-10 22:26:37 -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.
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.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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%