1
0
mirror of https://github.com/git/git.git synced 2025-04-13 18:22:17 +00:00
Jeff King 4f22b1015d do not stream large files to pack when filters are in use
Because git's object format requires us to specify the
number of bytes in the object in its header, we must know
the size before streaming a blob into the object database.
This is not a problem when adding a regular file, as we can
get the size from stat(). However, when filters are in use
(such as autocrlf, or the ident, filter, or eol
gitattributes), we have no idea what the ultimate size will
be.

The current code just punts on the whole issue and ignores
filter configuration entirely for files larger than
core.bigfilethreshold. This can generate confusing results
if you use filters for large binary files, as the filter
will suddenly stop working as the file goes over a certain
size.  Rather than try to handle unknown input sizes with
streaming, this patch just turns off the streaming
optimization when filters are in use.

This has a slight performance regression in a very specific
case: if you have autocrlf on, but no gitattributes, a large
binary file will avoid the streaming code path because we
don't know beforehand whether it will need conversion or
not. But if you are handling large binary files, you should
be marking them as such via attributes (or at least not
using autocrlf, and instead marking your text files as
such). And the flip side is that if you have a large
_non_-binary file, there is a correctness improvement;
before we did not apply the conversion at all.

The first half of the new t1051 script covers these failures
on input. The second half tests the matching output code
paths. These already work correctly, and do not need any
adjustment.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-24 14:18:20 -08:00
2012-02-05 23:52:53 -08:00
2011-10-16 03:01:44 -07:00
2011-04-27 11:36:42 -07:00
2011-03-17 15:30:49 -07:00
2011-10-21 16:04:32 -07:00
2011-12-13 10:18:12 -08:00
2011-05-09 16:29:46 -07:00
2011-07-19 09:54:51 -07:00
2011-02-27 23:29:03 -08:00
2011-10-21 16:04:32 -07:00
2011-10-07 15:46:14 -07:00
2011-05-26 16:47:15 -07:00
2011-08-11 12:21:07 -07:00
2011-09-19 20:46:48 -07:00
2011-04-28 14:11:39 -07:00
2012-02-05 23:50:52 -08:00
2011-08-20 22:33:58 -07:00
2011-07-22 14:43:21 -07:00
2011-12-13 16:34:44 -08:00
2012-02-05 23:52:53 -08:00
2011-11-08 13:37:10 -08:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2011-10-18 21:59:12 -07:00
2011-11-18 11:30:02 -08:00
2011-08-22 10:07:07 -07:00
2011-08-18 14:17:12 -07:00
2011-09-28 12:46:21 -07:00
2011-10-04 13:30:38 -07:00
2011-03-22 11:43:27 -07:00
2011-11-16 21:52:24 -08:00
2011-10-21 16:04:36 -07:00
2012-01-10 14:27:14 -08:00
2011-10-26 16:16:29 -07:00
2011-10-26 16:16:29 -07:00
2011-05-30 00:09:55 -07:00
2011-08-01 15:00:29 -07:00
2011-05-26 16:47:15 -07:00
2011-02-21 22:51:07 -08:00
2011-02-07 15:04:42 -08:00
2011-03-22 11:43:27 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2011-10-05 12:36:20 -07:00
2011-10-17 21:37:15 -07:00
2011-05-26 13:54:18 -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/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. 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 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%