1
0
mirror of https://github.com/git/git.git synced 2025-04-20 22:17:21 +00:00
Jeff King 6a36e1e7bb cat-file: default to --buffer when --batch-all-objects is used
Traditionally cat-file's batch-mode does not do any output
buffering. The reason is that a caller may have pipes
connected to its input and output, and would want to use
cat-file interactively, getting output immediately for each
input it sends.

This may involve a lot of small write() calls, which can be
slow. So we introduced --buffer to improve this, but we
can't turn it on by default, as it would break the
interactive case above.

However, when --batch-all-objects is used, we do not read
stdin at all. We generate the output ourselves as quickly as
possible, and then exit. In this case buffering is a strict
win, and it is simply a hassle for the user to have to
remember to specify --buffer.

This patch makes --buffer the default when --batch-all-objects
is used. Specifying "--buffer" manually is still OK, and you
can even override it with "--no-buffer" if you're a
masochist (or debugging).

For some real numbers, running:

  git cat-file --batch-all-objects --batch-check='%(objectname)'

on torvalds/linux goes from:

  real    0m1.464s
  user    0m1.208s
  sys     0m0.252s

to:

  real    0m1.230s
  user    0m1.172s
  sys     0m0.056s

for a 16% speedup.

Suggested-by: Charles Bailey <charles@hashpling.org>
Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-05-18 14:17:39 -07:00
2016-03-17 11:26:41 -07:00
2015-04-18 18:35:48 -07:00
2015-08-31 15:38:52 -07:00
2015-08-03 11:01:27 -07:00
2015-08-25 14:57:08 -07:00
2015-08-25 14:57:08 -07:00
2015-08-11 13:48:15 -07:00
2015-05-05 21:00:23 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2015-05-20 10:19:12 -07:00
2014-12-22 12:27:20 -08:00
2014-12-12 14:31:42 -08:00
2015-06-29 11:39:10 -07:00
2015-06-25 10:47:46 -07:00
2015-09-28 19:16:54 -07:00
2016-03-17 11:26:18 -07:00
2015-09-28 14:57:10 -07:00
2015-05-26 13:24:46 -07:00
2015-08-03 11:01:18 -07:00
2015-06-29 11:39:10 -07:00
2015-09-28 15:33:56 -07:00
2016-03-17 11:26:41 -07:00
2015-06-24 12:21:47 -07:00
2015-03-13 22:43:11 -07:00
2016-03-16 10:41:02 -07:00
2015-09-28 15:28:31 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:27 -07:00
2014-10-20 12:23:48 -07:00
2015-03-23 11:12:58 -07:00
2015-09-04 10:43:23 -07:00
2014-10-19 15:28:30 -07:00
2014-10-10 16:02:26 -07:00
2015-08-25 14:57:08 -07:00
2016-03-17 11:26:41 -07:00
2015-05-22 09:33:08 -07:00
2015-08-25 14:57:08 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2015-09-28 19:16:54 -07:00
2015-09-28 19:16:54 -07:00
2015-09-09 14:30:35 -07:00
2015-08-11 14:29:36 -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 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/giteveryday.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 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 866 MiB
Languages
C 49.9%
Shell 38.6%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%