René Scharfe 079f970971 name-rev: sort tip names before applying
name_ref() is called for each ref and checks if its a better name for
the referenced commit.  If that's the case it remembers it and checks if
a name based on it is better for its ancestors as well.  This in done in
the the order for_each_ref() imposes on us.

That might not be optimal.  If bad names happen to be encountered first
(as defined by is_better_name()), names derived from them may spread to
a lot of commits, only to be replaced by better names later.  Setting
better names first can avoid that.

is_better_name() prefers tags, short distances and old references.  The
distance is a measure that we need to calculate for each candidate
commit, but the other two properties are not dependent on the
relationships of commits.  Sorting the refs by them should yield better
performance than the essentially random order we currently use.

And applying older references first should also help to reduce rework
due to the fact that older commits have less ancestors than newer ones.

So add all details of names to the tip table first, then sort them
to prefer tags and older references and then apply them in this order.
Here's the performance as measures by hyperfine for the Linux repo
before:

Benchmark #1: ./git -C ../linux/ name-rev --all
  Time (mean ± σ):     851.1 ms ±   4.5 ms    [User: 806.7 ms, System: 44.4 ms]
  Range (min … max):   845.9 ms … 859.5 ms    10 runs

... and with this patch:

Benchmark #1: ./git -C ../linux/ name-rev --all
  Time (mean ± σ):     736.2 ms ±   8.7 ms    [User: 688.4 ms, System: 47.5 ms]
  Range (min … max):   726.0 ms … 755.2 ms    10 runs

Signed-off-by: René Scharfe <l.s.r@web.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2020-02-05 10:36:33 -08:00
2019-12-06 15:09:21 -08:00
2019-12-01 09:04:35 -08:00
2019-09-28 14:04:16 +09:00
2019-11-20 13:29:02 +09:00
2019-11-18 15:21:28 +09:00
2019-11-18 15:21:28 +09:00
2019-08-19 15:04:58 -07:00
2019-10-15 13:48:02 +09:00
2019-07-19 11:30:20 -07:00
2019-07-09 15:25:44 -07:00
2019-07-09 15:25:44 -07:00
2020-01-06 14:17:51 -08:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2019-12-25 11:21:58 -08:00
2019-11-10 16:00:54 +09:00
2019-11-22 16:11:44 +09:00
2019-12-06 16:31:39 +01:00
2019-12-01 09:04:36 -08:00
2019-12-06 16:31:39 +01:00
2019-11-13 11:48:47 +09:00
2019-12-01 09:04:36 -08:00
2019-11-10 16:00:54 +09:00
2019-07-09 15:25:43 -07:00
2019-05-05 15:20:10 +09:00
2019-12-05 12:52:43 -08:00
2019-12-16 13:08:39 -08:00
2019-10-15 13:48:02 +09:00
2019-12-25 11:22:02 -08:00
2019-12-25 11:21:58 -08:00
2019-12-25 11:21:58 -08:00
2019-12-06 16:31:39 +01:00
2019-12-09 22:17:55 -08:00
2019-07-25 13:59:20 -07:00
2019-12-09 22:17:55 -08:00
2020-01-02 12:38:29 -08:00
2020-01-13 10:16:43 -08:00
2019-11-18 15:21:28 +09:00
2019-11-10 16:00:54 +09:00
2019-12-01 09:04:35 -08:00
2019-08-30 10:22:42 -07:00
2019-11-13 10:09:10 +09:00
2019-12-01 09:04:33 -08:00
2019-08-15 12:37:10 -07:00
2019-04-22 11:14:43 +09:00
2019-11-18 15:21:28 +09:00
2018-08-29 13:05:35 -07:00
2019-12-25 11:22:01 -08:00
2019-01-14 12:13:04 -08:00
2019-10-23 12:05:05 +09:00
2019-12-01 09:04:35 -08:00
2019-07-19 11:30:20 -07:00
2019-07-19 11:30:20 -07:00
2019-05-05 15:20:10 +09:00
2019-12-09 22:17:55 -08:00
2019-12-16 13:08:39 -08:00
2019-12-02 08:48:56 -08:00
2019-12-10 13:11:43 -08:00
2019-02-05 14:26:09 -08:00
2018-11-02 12:14:21 +09:00
2019-11-27 10:57:10 +09:00
2019-10-15 13:48:02 +09:00
2019-10-15 13:48:02 +09:00
2018-08-15 15:08:23 -07:00
2019-11-18 15:21:28 +09:00
2019-04-01 11:57:39 +09:00
2019-12-06 16:31:40 +01:00
2019-11-10 16:00:54 +09:00
2019-05-05 15:20:10 +09:00
2019-09-30 13:19:26 +09:00
2019-10-11 14:24:46 +09:00
2019-11-13 10:09:10 +09:00
2019-10-11 14:24:48 +09:00
2019-02-05 14:26:11 -08:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:30 +01:00
2019-12-06 16:31:30 +01:00
2018-12-09 12:37:32 +09:00
2019-09-05 14:10:18 -07:00
2019-05-13 23:50:35 +09:00
2019-11-18 15:21:29 +09:00
2019-08-13 12:21:33 -07:00
2019-11-18 15:21:29 +09:00
2019-12-06 16:31:39 +01:00
2019-11-18 15:21:29 +09:00
2019-09-03 15:10:53 -07:00
2019-12-25 11:21:58 -08:00
2019-11-10 16:00:54 +09:00
2019-12-25 11:21:59 -08:00
2019-10-09 14:01:00 +09:00
2018-10-19 13:34:02 +09:00
2019-10-11 14:24:46 +09:00

Build Status

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-<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).

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://lore.kernel.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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
No description provided
Readme 604 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%