Johannes Sixt e7d5ce8165 mingw: avoid linking to the C library's isalpha()
The implementation of mingw_skip_dos_drive_prefix() calls isalpha() via
has_dos_drive_prefix(). Since the definition occurs long before isalpha()
is defined in git-compat-util.h, my build environment reports:

    CC alloc.o
In file included from git-compat-util.h:186,
                 from cache.h:4,
                 from alloc.c:12:
compat/mingw.h: In function 'mingw_skip_dos_drive_prefix':
compat/mingw.h:365: warning: implicit declaration of function 'isalpha'

Dscho does not see a similar warning in his build and suspects that
ctype.h is included somehow behind the scenes. This implies that his build
links to the C library's isalpha() and does not use git's isalpha().

To fix both the warning in my build and the inconsistency in Dscho's
build, move the function definition to mingw.c. Then it picks up git's
isalpha() because git-compat-util.h is included at the top of the file.

Signed-off-by: Johannes Sixt <j6t@kdbg.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-01-25 14:04:14 -08:00
2016-01-04 14:06:00 -08:00
2015-08-31 15:38:52 -07:00
2015-08-03 11:01:27 -07:00
2015-08-25 14:57:08 -07:00
2015-08-25 14:57:08 -07:00
2015-08-11 13:48:15 -07:00
2015-05-05 21:00:23 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:21 -07:00
2015-08-03 11:01:27 -07:00
2015-05-20 10:19:12 -07:00
2014-12-22 12:27:20 -08:00
2015-06-29 11:39:10 -07:00
2015-06-25 10:47:46 -07:00
2015-09-28 19:16:54 -07:00
2015-09-28 14:57:10 -07:00
2015-05-26 13:24:46 -07:00
2015-08-03 11:01:18 -07:00
2015-06-29 11:39:10 -07:00
2015-09-28 15:33:56 -07:00
2016-01-04 14:06:00 -08:00
2015-06-24 12:21:47 -07:00
2015-03-13 22:43:11 -07:00
2015-03-27 13:02:32 -07:00
2015-09-28 15:28:31 -07:00
2015-09-28 15:33:56 -07:00
2015-08-03 11:01:27 -07:00
2015-03-23 11:12:58 -07:00
2015-09-04 10:43:23 -07:00
2016-01-12 10:39:40 -08:00
2015-08-25 14:57:08 -07:00
2015-12-11 11:17:47 -08:00
2015-05-22 09:33:08 -07:00
2015-08-25 14:57:08 -07:00
2014-12-22 12:27:30 -08:00
2014-12-22 12:27:30 -08:00
2015-09-28 19:16:54 -07:00
2015-09-28 19:16:54 -07:00
2015-09-09 14:30:35 -07:00
2015-08-11 14:29:36 -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 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 697 MiB
Languages
C 50.5%
Shell 38.8%
Perl 4.4%
Tcl 3.2%
Python 0.8%
Other 2.1%