Linus Torvalds b59d398bea Do a better job at guessing unknown character sets
At least in the kernel development community, we're generally slowly
converting to UTF-8 everywhere, and the old default of Latin1 in emails is
being supplanted by UTF-8, and it doesn't necessarily show up as such in
the mail headers (because, quite frankly, when people send patches
around, they want the email client to do as little as humanly possible
about the patch)

Despite that, it's often the case that email addresses etc still have
Latin1, so I've seen emails where this is a mixed bag, with Signed-off
parts being copied from email (and containing Latin1 characters), and the
rest of the email being a patch in UTF-8.

So this suggests a very natural change: if the target character set is
utf-8 (the default), and if the source already looks like utf-8, just
assume that it doesn't need any conversion at all.

Only assume that it needs conversion if it isn't already valid utf-8, in
which case we (for historical reasons) will assume it's Latin1.

Basically no really _valid_ latin1 will ever look like utf-8, so while
this changes our historical behaviour, it doesn't do so in practice, and
makes the default behaviour saner for the case where the input was already
in proper format.

We could do a more fancy guess, of course, but this correctly handled a
series of patches I just got from Andrew that had a mixture of Latin1 and
UTF-8 (in different emails, but without any character set indication).

Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2007-07-18 17:01:10 -07:00
2007-07-12 14:14:51 -07:00
2007-07-12 14:38:36 -07:00
2007-07-02 01:45:57 -07:00
2007-07-14 13:44:58 -07:00
2007-07-07 12:29:09 -07:00
2007-06-08 02:37:19 -07:00
2007-06-13 02:02:10 -07:00
2007-06-22 23:19:43 -07:00
2007-06-13 00:41:21 -07:00
2007-06-13 02:02:10 -07:00
2007-06-13 02:02:10 -07:00
2007-06-08 02:37:19 -07:00
2007-07-07 11:53:49 -07:00
2007-06-22 23:37:11 -07:00
2007-07-02 01:45:12 -07:00
2007-07-18 17:00:36 -07:00
2007-07-04 10:09:32 -07:00
2007-06-26 18:45:29 -07:00
2007-06-13 02:02:10 -07:00
2007-07-02 22:52:14 -07:00
2007-07-02 22:52:14 -07:00
2007-07-12 14:54:33 -07:00
2007-07-15 15:23:36 -07:00
2007-07-05 23:22:12 -07:00
2007-07-17 01:33:04 -07:00
2007-07-04 10:09:32 -07:00
2007-06-08 02:54:57 -07:00
2007-07-02 17:12:48 -07:00
2007-07-12 12:01:47 -07:00
2007-06-08 02:37:19 -07:00
2007-07-11 13:52:16 -07:00
2007-07-11 13:52:16 -07:00
2007-07-03 22:56:59 -07:00
2007-06-22 23:37:21 -07:00
2007-06-22 23:19:43 -07:00
2007-06-08 02:54:57 -07:00
2007-06-08 02:37:19 -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.
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 646 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%