Ramsay Jones 3f789719a6 archive-tar: fix a sparse 'constant too large' warning
Commit dddbad728c ("timestamp_t: a new data type for timestamps",
26-04-2017) introduced a new typedef 'timestamp_t', as a synonym for an
unsigned long, which was used at the time to represent timestamps in
git. A later commit 28f4aee3fb ("use uintmax_t for timestamps",
26-04-2017) changed the typedef to use an 'uintmax_t' for the timestamp
representation type.

When building on a 32-bit Linux system, sparse complains that a constant
(USTAR_MAX_MTIME) used to detect a 'far-future mtime' timestamp, is too
large; 'warning: constant 077777777777UL is so big it is unsigned long
long' on lines 335 and 338 of archive-tar.c. Note that both gcc and
clang only issue a warning if this constant is used in a context that
requires an 'unsigned long' (rather than an uintmax_t). (Since TIME_MAX
is no longer equal to 0xFFFFFFFF, even on a 32-bit system, the macro
USTAR_MAX_MTIME is set to 077777777777UL, which cannot be represented as
an 'unsigned long' constant).

In order to suppress the warning, change the definition of the macro
constant USTAR_MAX_MTIME to use an 'ULL' type suffix.

In a similar vein, on systems which use a 64-bit representation of the
'unsigned long' type, the USTAR_MAX_SIZE constant macro is defined with
the value 077777777777ULL. Although this does not cause any warning
messages to be issued, it would be more appropriate for this constant
to use an 'UL' type suffix rather than 'ULL'.

Signed-off-by: Ramsay Jones <ramsay@ramsayjones.plus.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-05-09 11:23:14 +09:00
2017-02-16 14:45:13 -08:00
2016-10-20 09:33:17 -07:00
2017-03-26 15:34:44 -07:00
2017-03-24 13:31:01 -07:00
2017-03-13 15:28:54 -07:00
2017-03-13 15:28:54 -07:00
2017-04-19 21:37:13 -07:00
2016-05-09 12:29:08 -07:00
2017-04-19 21:37:13 -07:00
2017-01-25 14:42:37 -08:00
2016-08-12 09:47:37 -07:00
2017-04-19 21:37:24 -07:00
2016-05-09 12:29:08 -07:00
2017-04-19 21:37:13 -07:00
2017-03-31 08:33:56 -07:00
2016-09-29 15:42:18 -07:00
2016-12-12 15:15:07 -08:00
2016-05-09 12:29:08 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-04-27 13:07:40 +09:00
2016-12-19 14:45:35 -08:00
2017-04-19 21:42:08 -07:00
2017-02-15 12:54:19 -08:00
2017-03-17 10:40:25 -07:00
2017-03-22 13:41:41 -07:00
2017-03-22 13:41:41 -07:00
2017-01-30 14:17:00 -08:00
2016-12-07 11:31:59 -08:00
2017-04-19 21:37:25 -07:00
2016-12-07 11:31:59 -08:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2017-03-31 20:57:18 -07:00
2016-09-26 16:09:18 -07:00
2017-01-30 14:17:00 -08:00
2017-02-08 15:39:55 -08:00
2017-02-08 15:39:55 -08:00
2017-01-30 14:17:00 -08:00
2017-03-28 14:05:59 -07:00
2017-04-19 21:37:19 -07:00
2017-01-30 14:17:00 -08:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2017-04-19 21:37:13 -07:00
2017-03-28 13:54:14 -07:00
2017-04-19 21:37:13 -07:00
2016-04-25 15:17:15 -07:00
2017-04-19 21:37:13 -07:00
2017-03-31 08:33:56 -07:00
2016-09-29 15:42:18 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2017-03-31 08:33:56 -07:00
2016-07-01 15:09:10 -07:00
2016-08-05 09:28:17 -07:00
2016-09-29 15:42:18 -07:00
2017-01-31 13:14:56 -08:00
2016-09-26 18:16:23 -07:00

Git - fast, scalable, distributed revision control system

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.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.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).

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 https://public-inbox.org/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.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (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
Description
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%