1
0
mirror of https://github.com/git/git.git synced 2025-04-06 09:08:09 +00:00
Nick Alcock ebaa1bd407 Support sizes >=2G in various config options accepting 'g' sizes.
The config options core.packedGitWindowSize, core.packedGitLimit,
core.deltaBaseCacheLimit, core.bigFileThreshold, pack.windowMemory and
pack.packSizeLimit all claim to support suffixes up to and including
'g'.  This implies that they should accept sizes >=2G on 64-bit
systems: certainly, specifying a size of 3g should not silently be
translated to zero or transformed into a large negative value due to
integer overflow.  However, due to use of git_config_int() rather than
git_config_ulong(), that is exactly what happens:

% git config core.bigFileThreshold 2g
% git gc --aggressive # with extra debugging code to print out
                      # core.bigfilethreshold after parsing
bigfilethreshold: -2147483648
[...]

This is probably irrelevant for core.deltaBaseCacheLimit, but is
problematic for the other values.  (It is particularly problematic for
core.packedGitLimit, which can't even be set to its default value in
the config file due to this bug.)

This fixes things for 32-bit platforms as well.  They get the usual bad
config error if an overlarge value is specified, e.g.:

fatal: bad config value for 'core.bigfilethreshold' in /home/nix/.gitconfig

This is detected in all cases, even if the 32-bit platform has no size
larger than 'long'.  For signed integral configuration values, we also
detect the case where the value is too large for the signed type but
not the unsigned type.

Signed-off-by: Nick Alcock <nix@esperi.org.uk>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2011-11-05 23:10:43 -07:00
2011-06-20 14:27:36 -07:00
2011-06-26 12:09:11 -07:00
2011-06-26 12:41:16 -07:00
2011-03-26 10:42:35 -07:00
2011-06-21 14:56:59 -07:00
2011-06-20 14:49:44 -07:00
2011-04-27 11:36:42 -07:00
2011-05-26 10:31:57 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2011-03-17 15:30:49 -07:00
2011-02-13 15:13:41 -08:00
2011-02-06 22:50:26 -08:00
2011-05-31 12:19:11 -07:00
2011-05-09 16:29:46 -07:00
2009-09-13 01:32:26 -07:00
2011-03-22 10:16:54 -07:00
2011-06-06 11:40:14 -07:00
2011-06-06 11:40:14 -07:00
2011-06-06 11:40:14 -07:00
2010-05-07 09:34:27 -07:00
2011-05-06 10:50:06 -07:00
2011-05-02 15:58:30 -07:00
2011-05-19 20:37:21 -07:00
2011-04-28 14:11:39 -07:00
2011-04-28 14:11:39 -07:00
2010-06-13 20:02:50 -07:00
2011-05-30 00:09:55 -07:00
2011-05-20 18:50:29 -07:00
2011-06-26 12:41:16 -07:00
2010-06-30 15:49:18 -07:00
2011-05-09 16:29:33 -07:00
2011-05-09 16:29:33 -07:00
2010-01-21 20:03:45 -08:00
2011-05-26 10:32:19 -07:00
2010-11-24 15:13:58 -08:00
2011-05-19 18:23:17 -07:00
2010-08-26 09:20:03 -07:00
2011-05-31 12:19:11 -07:00
2010-10-13 19:11:26 -07:00
2010-01-12 01:06:09 -08:00
2010-04-01 23:58:30 -07:00
2011-03-22 10:16:54 -07:00
2011-05-31 12:19:11 -07:00
2011-02-07 15:15:17 -08:00
2011-03-22 11:43:27 -07:00
2011-06-16 10:33:50 -07:00
2011-05-31 12:06:40 -07:00
2011-05-30 00:09:55 -07:00
2011-05-31 12:19:11 -07:00
2011-05-30 00:09:55 -07:00
2011-05-25 16:23:26 -07:00
2011-05-23 09:58:35 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2011-04-27 11:36:43 -07:00
2011-02-21 22:51:07 -08:00
2011-02-07 15:04:42 -08:00
2009-08-23 17:11:28 -07:00
2010-08-14 19:35:37 -07: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-03-22 11:43:27 -07:00
2011-05-30 00:09:55 -07:00
2011-03-22 10:16:54 -07:00
2011-03-22 10:16:54 -07:00
2010-04-02 00:05:31 -07:00
2011-05-26 13:54:18 -07:00
2011-04-01 17:55:55 -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 809 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%