Jeff King 260d408e32 config: use getc_unlocked when reading from file
We read config files character-by-character from a stdio
handle using fgetc(). This incurs significant locking
overhead, even though we know that only one thread can
possibly access the handle. We can speed this up by taking
the lock ourselves, and then using getc_unlocked to read
each character.

On a silly pathological case:

  perl -le '
    print "[core]";
    print "key$_ = value$_" for (1..1000000)
  ' >input
  git config -f input core.key1

this dropped the time to run git-config from:

  real    0m0.263s
  user    0m0.260s
  sys     0m0.000s

to:

  real    0m0.159s
  user    0m0.152s
  sys     0m0.004s

for a savings of 39%.  Most config files are not this big,
but the savings should be proportional to the size of the
file (i.e., we always save 39%, just of a much smaller
number).

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2015-04-16 08:15:05 -07:00
2014-02-27 14:01:48 -08:00
2015-03-26 11:59:05 -07:00
2014-06-26 13:44:11 -07:00
2015-03-15 17:25:02 +11:00
2015-03-26 11:57:14 -07:00
2015-01-14 09:32:04 -08:00
2014-07-28 10:14:33 -07:00
2015-03-17 16:01:27 -07:00
2015-01-14 09:32:04 -08:00
2014-05-15 09:49:12 -07:00
2014-05-15 09:49:12 -07:00
2015-01-07 12:55:05 -08:00
2015-03-10 20:53:52 -07:00
2015-01-07 12:55:05 -08:00
2013-12-09 14:54:48 -08:00
2014-12-22 12:27:20 -08:00
2014-12-12 14:31:42 -08:00
2014-03-31 15:29:27 -07:00
2014-06-03 12:06:40 -07:00
2014-01-17 12:21:20 -08:00
2014-12-22 12:27:41 -08:00
2014-10-29 10:09:35 -07:00
2015-02-11 13:39:44 -08:00
2015-02-26 20:19:21 +00:00
2015-03-26 11:59:05 -07:00
2014-10-08 13:05:25 -07:00
2014-09-29 12:36:11 -07:00
2014-07-07 13:56:38 -07:00
2014-07-07 13:56:38 -07:00
2015-03-06 15:02:25 -08:00
2014-11-03 11:00:28 -08:00
2014-10-20 12:23:48 -07:00
2015-03-20 13:11:49 -07:00
2015-01-07 12:55:05 -08:00
2013-07-29 12:32:25 -07:00
2014-10-19 15:28:30 -07:00
2014-10-19 15:28:30 -07:00
2015-02-11 13:44:07 -08:00
2014-12-17 11:46:57 -08:00
2014-07-21 12:35:39 -07:00
2014-03-31 15:29:27 -07:00
2014-10-10 16:02:26 -07:00
2015-03-23 11:27:27 -07:00
2015-02-11 13:44:07 -08:00
2014-09-15 11:29:46 -07:00
2015-02-11 13:44:07 -08:00
2015-02-11 13:43:51 -08:00
2014-09-02 13:28:44 -07:00
2014-06-13 11:49:40 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2015-03-22 21:39:16 -07:00
2014-03-31 15:29:27 -07:00
2015-03-22 21:39:18 -07:00
2015-03-25 12:54:25 -07:00
2015-01-07 19:56:44 -08:00
2014-09-02 13:28:44 -07:00
2014-12-18 12:30:53 -08:00
2015-01-07 13:28:10 -08:00
2014-12-17 11:04:39 -08: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/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).

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
No description provided
Readme 575 MiB
Languages
C 50.4%
Shell 38.7%
Perl 4.4%
Tcl 3.1%
Python 0.8%
Other 2.4%