Junio C Hamano 201ac8efc7 Fix 'crlf' attribute semantics.
Earlier we said 'crlf lets the path go through core.autocrlf
process while !crlf disables it altogether'.  This fixes the
semantics to:

 - Lack of 'crlf' attribute makes core.autocrlf to apply
   (i.e. we guess based on the contents and if platform
   expresses its desire to have CRLF line endings via
   core.autocrlf, we do so).

 - Setting 'crlf' attribute to true forces CRLF line endings in
   working tree files, even if blob does not look like text
   (e.g. contains NUL or other bytes we consider binary).

 - Setting 'crlf' attribute to false disables conversion.

Signed-off-by: Junio C Hamano <junkio@cox.net>
2007-04-15 13:35:45 -07:00
2007-04-05 16:34:51 -07:00
2007-04-14 04:18:46 -07:00
2007-02-03 21:49:54 -08:00
2007-04-14 08:57:06 -07:00
2007-04-14 08:57:06 -07:00
2007-04-07 02:26:24 -07:00
2007-04-07 02:26:24 -07:00
2007-02-27 22:15:42 -08:00
2007-04-11 18:43:01 -07:00
2007-03-17 00:34:19 -07:00
2007-04-12 21:04:27 -07:00
2007-04-07 02:26:24 -07:00
2007-03-20 22:17:47 -07:00
2007-04-05 16:34:51 -07:00
2007-02-24 01:42:06 -08:00
2006-05-01 22:29:16 -07:00
2007-04-11 20:02:03 -07:00
2007-03-02 00:37:12 -08:00
2007-03-27 13:00:13 -07:00
2007-04-15 13:35:45 -07:00
2005-12-27 10:49:25 -08:00
2006-05-15 12:32:13 -07:00
2007-04-14 08:57:06 -07:00
2007-03-14 16:21:19 -07:00
2006-03-05 02:47:29 -08:00
2007-04-08 23:27:22 -07:00
2006-02-06 21:43:27 -08:00
2007-02-03 21:49:54 -08:00
2007-04-07 02:29:40 -07:00
2007-01-18 14:22:24 -08:00
2007-01-30 21:03:11 -08:00
2007-04-11 17:19:36 -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-04-03 23:44:32 -07:00
2006-06-26 14:58:41 -07:00
2007-04-07 02:29:40 -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-04-12 21:04:27 -07:00
2007-04-11 20:02:03 -07:00
2007-03-12 23:40:18 -07:00
2007-03-10 22:07:26 -08:00
2006-10-20 16:50:36 -07:00
2007-02-27 01:34:21 -08:00
2006-03-25 16:35:43 -08:00
2007-03-03 19:47:46 -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.
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
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%