Johannes Schindelin bcad1e6d58 Merge branch 'utf8-environment'
A long time ago, we decided to convert the entire environment to UTF-8
upon startup, and only work on a copy. This was responsible for several
serious bugs, because 3rd-party libraries (such as curl) are free to
work on the environment, too, and they had no idea about *our*
environment, and segmentation faults were the consequence.

In the meantime, Git consolidated a lot of `getenv()` calls (because it
is not really safe to hold onto the returned pointers for too long, and
also it is better to keep a copy and have a consistent state throughout
the lifetime of the process).

So the main reason for that wholesale conversion (performance) is
probably no longer valid.

As a matter of fact, for the MSVC-specific startup code, we could not
even make that startup conversion work because we have no longer access
to that (private) pointer to the environment of the MSVC runtime.

The plan, of course, is to consolidate those two divergent code paths by
using the newer, safer environment handling (which converts on the fly
with every getenv()/setenv() call).

There are already preliminary patches to that end in the
'unify-gcc-msvc-env-handling' branch on dscho/git, but we need to make
sure that this *really* does not regress performance, probably by adding
some code that accumulates stats (how often/how many nanoseconds spent),
and writes the numbers out in an atexit() handler, then run the test
suite and compare numbers.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
2018-10-12 22:57:33 +02:00
2018-10-04 21:52:25 +02:00
2018-10-11 14:52:30 +02:00
2018-10-12 22:57:31 +02:00
2018-08-02 13:54:58 -07:00
2018-10-12 22:57:32 +02:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 11:33:53 -07:00
2018-08-13 14:14:43 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 12:41:32 -07:00
2018-07-26 10:12:51 -07:00
2018-10-11 13:38:36 +02:00
2018-10-11 23:11:12 +02:00
2018-08-20 12:41:32 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-08-20 12:41:32 -07:00
2018-08-02 15:30:43 -07:00
2018-09-27 11:50:45 -07:00
2018-08-01 13:37:18 -07:00
2018-09-27 11:52:33 -07:00
2018-10-04 21:52:25 +02:00
2018-08-02 15:30:44 -07:00
2018-08-02 15:30:44 -07:00
2018-10-12 22:46:10 +02:00
2018-08-02 15:30:45 -07:00
2018-08-15 15:08:23 -07:00
2018-10-11 14:52:53 +02:00
2018-08-15 15:08:25 -07:00
2018-08-15 15:08:23 -07:00
2018-09-27 11:52:33 -07:00
2018-08-20 11:33:50 -07:00
2018-08-15 15:08:23 -07:00
2018-08-20 12:41:32 -07:00
2018-08-20 11:33:53 -07:00
2018-10-04 21:52:25 +02:00
2018-09-27 11:50:45 -07:00
2018-08-02 15:30:39 -07:00
2018-08-15 11:52:09 -07:00
2018-08-21 17:07:50 +02:00
2018-08-20 12:41:32 -07:00

Build Status

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 https://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.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

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 678 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%