Kirill Smelkov 7e9003c149 tree-diff: show_tree() is not needed
We don't need special code for showing added/removed subtree, because we
can do the same via diff_tree_sha1, just passing NULL for absent tree.

And compared to show_tree(), which was calling show_entry() for every
tree entry, that would lead to the same show_entry() callings:

    show_tree(t):
        for e in t.entries:
            show_entry(e)

    diff_tree_sha1(NULL, new):  /* the same applies to (old, NULL) */
        diff_tree(t1=NULL, t2)
            ...
            if (!t1->size)
                show_entry(t2)
            ...

and possible overhead is negligible, since after the patch, timing for

    `git log --raw --no-abbrev --no-renames`

for navy.git and `linux.git v3.10..v3.11` is practically the same.

So let's say goodbye to show_tree() - it removes some code, but also,
and what is important, consolidates more code for showing/recursing into
trees into one place.

Signed-off-by: Kirill Smelkov <kirr@mns.spb.ru>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2014-03-04 13:33:47 -08:00
2014-01-27 10:45:49 -08:00
2014-01-27 10:44:59 -08:00
2014-01-27 11:01:35 -08:00
2013-12-12 14:18:34 -08:00
2014-01-10 10:32:18 -08:00
2013-11-12 13:32:11 -08:00
2014-01-17 12:21:20 -08:00
2013-12-17 12:02:44 -08:00
2014-01-17 12:21:20 -08:00
2013-12-09 14:54:48 -08:00
2014-01-17 12:21:20 -08:00
2014-01-10 10:33:09 -08:00
2014-01-10 10:33:09 -08:00
2014-01-27 10:45:03 -08:00
2013-09-11 15:03:28 -07:00
2014-01-17 12:21:20 -08:00
2014-01-17 12:21:20 -08:00
2013-11-12 09:24:27 -08:00
2014-01-10 10:33:14 -08:00
2013-10-29 12:41:17 -07:00
2014-01-31 14:16:06 -08:00
2014-01-17 12:21:20 -08:00
2013-12-17 12:02:44 -08:00
2013-12-05 12:58:59 -08:00
2014-01-10 10:32:39 -08:00
2013-10-23 13:21:31 -07:00
2013-10-23 13:21:31 -07:00
2014-01-10 10:33:09 -08:00
2014-01-13 11:33:35 -08:00
2014-01-10 10:31:48 -08:00
2013-11-01 07:38:58 -07:00
2014-01-13 11:28:26 -08:00
2014-01-17 12:21:20 -08:00
2014-01-17 12:21:20 -08:00
2013-09-09 14:36:15 -07:00
2013-09-09 14:36:15 -07:00
2013-12-05 12:59:09 -08:00
2013-10-31 13:48:26 -07:00
2014-01-17 12:21:20 -08:00
2014-01-17 12:21:20 -08:00
2014-01-27 10:44:59 -08:00
2014-01-17 12:21:20 -08:00
2013-09-17 11:37:33 -07:00
2013-09-17 11:37:33 -07:00
2014-01-17 12:21:20 -08:00
2013-11-12 09:24:27 -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.
S
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 544 MiB
Languages
C 50.4%
Shell 38.9%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.2%