1
0
mirror of https://github.com/git/git.git synced 2025-03-20 22:42:34 +00:00
Junio C Hamano c075aea5da name-rev: tolerate clock skew in committer dates
In git.git repository, "git-name-rev v1.3.0~158" cannot name the
rev, while adjacent revs can be named.

This was because it gives up traversal from the tips of existing
refs as soon as it sees a commit that has older commit timestamp
than what is being named.  This is usually a good heuristics,
but v1.3.0~158 has a slightly older commit timestamp than
v1.3.0~157 (i.e. it's child), as these two were made in a
separate repostiory (in fact, in a different continent).

This adds a hardcoded slop value (1 day) to the cut-off
heuristics to work this kind of problem around.  The current
algorithm essentially runs around from the available tips down
to ancient commits and names every single rev available that are
newer than cut-off date, so a single day slop would not add that
much overhead in repositories with long enough history where the
performance of name-rev matters.

I think the algorithm could be made a bit smarter by deepening
the graph on demand as a new commit is asked to be named (this
would require rewriting of name_rev() function not to recurse
itself but use a traversal list like revision.c traverser does),
but that would be a separate issue.

Acked-by: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-05-24 13:36:54 -07:00
2007-05-03 22:36:32 -07:00
2007-02-03 21:49:54 -08:00
2007-05-21 18:36:02 -07:00
2007-03-14 01:40:19 -07:00
2007-05-10 13:26:26 -07:00
2007-05-05 22:40:27 -07:00
2007-02-27 22:15:42 -08:00
2007-03-17 00:34:19 -07:00
2007-03-20 22:17:47 -07:00
2007-03-27 16:57:26 -07:00
2007-02-24 01:42:06 -08:00
2007-03-17 00:34:19 -07:00
2006-05-01 22:29:16 -07:00
2007-03-02 00:37:12 -08:00
2006-11-21 20:55:39 -08:00
2007-02-18 15:57:36 -08:00
2007-03-27 13:00:13 -07:00
2007-02-14 11:19:28 -08:00
2005-12-27 10:49:25 -08:00
2005-08-09 22:28:19 -07:00
2005-10-14 17:17:27 -07:00
2006-05-15 12:32:13 -07:00
2007-03-14 16:21:19 -07:00
2007-04-23 01:44:00 -07:00
2006-12-29 11:01:31 -08:00
2006-03-05 02:47:29 -08:00
2007-04-23 22:14:24 -07:00
2006-02-06 21:43:27 -08:00
2007-02-03 21:49:54 -08:00
2005-09-07 17:45:20 -07:00
2007-01-18 14:22:24 -08:00
2007-01-30 21:03:11 -08:00
2007-05-20 00:15:53 -07:00
2006-09-27 23:59:09 -07:00
2007-03-27 16:57:57 -07:00
2007-03-07 10:47:10 -08:00
2007-03-07 10:47:10 -08:00
2007-05-05 21:09:34 -07:00
2006-06-26 14:58:41 -07:00
2007-03-19 02:48:37 -07:00
2007-02-27 01:34:21 -08:00
2007-03-07 10:47:10 -08:00
2007-02-08 17:48:22 -08:00
2007-02-03 11:57:18 -08:00
2007-05-20 00:15:53 -07:00
2007-03-12 23:40:18 -07:00
2007-03-10 22:07:26 -08:00
2007-03-12 11:30:38 -07:00
2006-10-20 16:50:36 -07:00
2007-02-27 01:34:21 -08:00
2005-11-02 16:50:58 -08:00
2006-03-25 16:35:43 -08:00
2007-05-01 02:59:08 -07:00
2007-05-07 22:02:40 -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/tutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands,
and "man git-commandname" for documentation of each command.
CVS users may also want to read Documentation/cvs-migration.txt.

Many Git online resources are accessible from http://git.or.cz/
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 795 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%