1
0
mirror of https://github.com/git/git.git synced 2025-03-24 14:01:08 +00:00
Jeff King d4b8de0420 fsck: report integer overflow in author timestamps
When we check commit objects, we complain if commit->date is
ULONG_MAX, which is an indication that we saw integer
overflow when parsing it. However, we do not do any check at
all for author lines, which also contain a timestamp.

Let's actually check the timestamps on each ident line
with strtoul. This catches both author and committer lines,
and we can get rid of the now-redundant commit->date check.

Note that like the existing check, we compare only against
ULONG_MAX. Now that we are calling strtoul at the site of
the check, we could be slightly more careful and also check
that errno is set to ERANGE. However, this will make further
refactoring in future patches a little harder, and it
doesn't really matter in practice.

For 32-bit systems, one would have to create a commit at the
exact wrong second in 2038. But by the time we get close to
that, all systems will hopefully have moved to 64-bit (and
if they haven't, they have a real problem one second later).

For 64-bit systems, by the time we get close to ULONG_MAX,
all systems will hopefully have been consumed in the fiery
wrath of our expanding Sun.

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