Johannes Schindelin 8abfdf44c8 tests: explicitly use git.exe on Windows
On Windows, when we refer to `/an/absolute/path/to/git`, it magically
resolves `git.exe` at that location. Except if something of the name
`git` exists next to that `git.exe`. So if we call `$BUILD_DIR/git`, it
will find `$BUILD_DIR/git.exe` *only* if there is not, say, a directory
called `$BUILD_DIR/git`.

Such a directory, however, exists in Git for Windows when building with
Visual Studio (our Visual Studio project generator defaults to putting
the build files into a directory whose name is the base name of the
corresponding `.exe`).

In the bin-wrappers/* scripts, we already take pains to use `git.exe`
rather than `git`, as this could pick up the wrong thing on Windows
(i.e. if there exists a `git` file or directory in the build directory).

Now we do the same in the tests' start-up code.

This also helps when testing an installed Git, as there might be even
more likely some stray file or directory in the way.

Note: the only way we can record whether the `.exe` suffix is by writing
it to the `GIT-BUILD-OPTIONS` file and sourcing it at the beginning of
`t/test-lib.sh`. This is not a requirement introduced by this patch, but
we move the call to be able to use the `$X` variable that holds the file
extension, if any.

Note also: the many, many calls to `git this` and `git that` are
unaffected, as the regular PATH search will find the `.exe` files on
Windows (and not be confused by a directory of the name `git` that is
in one of the directories listed in the `PATH` variable), while
`/path/to/git` would not, per se, know that it is looking for an
executable and happily prefer such a directory.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2018-11-16 14:18:00 +09:00
2018-11-13 22:37:28 +09:00
2018-11-02 11:04:53 +09:00
2018-10-16 16:16:01 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-11-02 11:04:53 +09:00
2018-10-19 13:34:02 +09:00
2018-11-02 11:04:55 +09:00
2018-11-13 22:37:20 +09:00
2018-10-19 13:34:02 +09:00
2018-11-13 22:37:27 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-11-13 22:37:20 +09:00
2018-09-17 13:53:57 -07:00
2018-10-30 15:43:48 +09:00
2018-09-27 11:52:33 -07:00
2018-11-02 11:04:53 +09:00
2018-10-19 13:34:02 +09:00
2018-11-03 00:53:59 +09:00
2018-10-30 15:43:39 +09:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:57 -07:00
2018-11-13 22:37:19 +09:00
2018-11-13 22:37:19 +09:00
2018-10-19 13:34:02 +09:00
2018-09-17 13:53:52 -07:00
2018-10-04 11:12:14 -07:00
2018-10-04 11:12:14 -07:00
2018-10-19 13:34:02 +09:00
2018-11-03 00:53:58 +09:00
2018-11-13 22:37:27 +09:00
2018-09-17 13:53:52 -07:00
2018-11-13 22:37:26 +09:00
2018-09-17 13:53:57 -07:00
2018-11-02 11:04:54 +09:00
2018-11-02 11:04:54 +09:00
2018-09-17 13:53:54 -07:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00
2018-10-19 13:34:02 +09:00

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 235 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.3%
Python 0.8%
Other 2%