Junio C Hamano 116eb3abfe parse_date(): allow ancient git-timestamp
The date-time parser parses out a human-readble datestring piece by
piece, so that it could even parse a string in a rather strange
notation like 'noon november 11, 2005', but restricts itself from
parsing strings in "<seconds since epoch> <timezone>" format only
for reasonably new timestamps (like 1974 or newer) with 10 or more
digits. This is to prevent a string like "20100917" from getting
interpreted as seconds since epoch (we want to treat it as September
17, 2010 instead) while doing so.

The same codepath is used to read back the timestamp that we have
already recorded in the headers of commit and tag objects; because
of this, such a commit with timestamp "0 +0000" cannot be rebased or
amended very easily.

Teach parse_date() codepath to special case a string of the form
"<digits> +<4-digits>" to work this issue around, but require that
there is no other cruft around the string when parsing a timestamp
of this format for safety.

Note that this has a slight backward incompatibility implications.

If somebody writes "git commit --date='20100917 +0900'" and wants it
to mean a timestamp in September 2010 in Japan, this change will
break such a use case.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
2012-02-03 23:11:32 -08:00
2011-08-28 22:03:26 -07:00
2011-09-30 14:20:57 -07:00
2011-03-26 10:42:35 -07:00
2011-04-27 11:36:42 -07:00
2011-09-06 11:42:58 -07:00
2011-03-17 15:30:49 -07:00
2011-08-28 21:19:12 -07:00
2011-09-16 21:47:47 -07:00
2011-08-28 21:22:58 -07: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-03-22 10:16:54 -07:00
2011-08-28 21:19:16 -07:00
2011-08-28 21:19:16 -07:00
2011-08-20 22:33:57 -07:00
2011-05-06 10:50:06 -07:00
2011-05-02 15:58:30 -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
2011-08-25 16:00:16 -07:00
2011-09-30 14:20:57 -07:00
2011-08-20 22:33:58 -07:00
2011-07-22 14:43:21 -07:00
2011-08-11 11:03:13 -07:00
2011-08-16 11:23:26 -07:00
2011-05-26 10:32:19 -07:00
2011-08-28 22:03:26 -07:00
2011-08-20 22:33:57 -07:00
2011-05-19 18:23:17 -07:00
2011-08-28 21:22:58 -07:00
2011-08-22 10:07:07 -07:00
2011-08-18 14:17:12 -07:00
2011-05-31 12:19:11 -07:00
2011-03-22 11:43:27 -07:00
2011-08-25 16:00:07 -07:00
2011-08-17 17:35:38 -07:00
2011-09-23 14:43:05 -07:00
2011-09-06 11:42:12 -07:00
2011-06-07 16:07:07 -07:00
2011-06-07 16:07:07 -07:00
2011-05-30 00:09:55 -07:00
2011-05-31 12:19:11 -07:00
2011-08-01 16:21:55 -07:00
2011-08-28 21:20:28 -07:00
2011-05-23 09:58:35 -07:00
2011-08-01 15:00:29 -07:00
2011-05-26 16:47:15 -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-09-06 11:42:12 -07:00
2011-08-24 12:18:02 -07:00
2011-03-22 10:16:54 -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
No description provided
Readme 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%