SZEDER Gábor 824388d54b completion: let 'for-each-ref' filter remote branches for 'checkout' DWIMery
The code listing unique remote branches for 'git checkout's tracking
DWIMery outputs only remote branches that match the current word to be
completed, but the filtering is done in a shell loop iterating over
all remote refs.

Let 'git for-each-ref' do the filtering, as it can do so much more
efficiently and we can remove that shell loop entirely.

This speeds up refs completion for 'git checkout' considerably when
there are a lot of non-matching remote refs to be filtered out.
Uniquely completing a branch in a repository with 100k remote
branches, all packed, best of five:

  On Linux, before:

    $ time __git_complete_refs --cur=maste --track

    real    0m1.993s
    user    0m1.740s
    sys     0m0.304s

  After:

    real    0m0.266s
    user    0m0.248s
    sys     0m0.012s

  On Windows, before:

    real    0m6.187s
    user    0m3.358s
    sys     0m2.121s

  After:

    real    0m0.750s
    user    0m0.015s
    sys     0m0.090s

Signed-off-by: SZEDER Gábor <szeder.dev@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2017-03-23 11:18:22 -07:00
2016-05-10 11:19:07 -07:00
2016-02-22 14:51:09 -08:00
2016-12-27 00:11:40 -08:00
2017-01-25 14:42:37 -08:00
2017-02-02 13:36:57 -08:00
2017-02-02 13:36:55 -08:00
2016-02-22 14:51:09 -08:00
2016-11-22 13:55:20 -08:00
2016-11-22 13:55:20 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2017-01-25 14:42:37 -08:00
2016-08-12 09:47:37 -07:00
2016-12-06 13:27:11 -08:00
2016-10-31 13:15:21 -07:00
2016-05-09 12:29:08 -07:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2016-10-27 14:58:50 -07:00
2016-09-29 15:42:18 -07:00
2017-01-18 15:12:16 -08:00
2016-12-12 15:15:07 -08:00
2016-05-09 12:29:08 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2017-01-23 11:02:36 -08:00
2017-02-02 13:36:55 -08:00
2016-12-19 14:45:35 -08:00
2016-10-14 01:36:12 +00:00
2017-02-03 11:29:52 -08:00
2016-02-22 14:51:09 -08:00
2016-09-29 15:42:18 -07:00
2016-05-17 14:38:32 -07:00
2016-12-07 11:31:59 -08:00
2017-02-02 13:36:57 -08: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
2016-09-26 16:09:18 -07:00
2015-11-20 08:02:05 -05:00
2016-06-13 14:38:16 -07:00
2016-09-29 15:42:18 -07:00
2016-09-25 16:44:13 -07:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2017-01-31 13:15:00 -08:00
2017-01-31 13:14:58 -08:00
2017-01-17 15:19:11 -08:00
2016-04-25 15:17:15 -07:00
2016-07-14 15:50:41 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:46 -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-02-22 10:40:35 -08:00
2016-09-26 18:16:23 -07:00
2017-02-02 13:36:55 -08:00
2017-02-03 11:25:19 -08: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 http://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
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%