Jeff King b1ef400eec setup_git_env: avoid blind fall-back to ".git"
When we default to ".git" without having done any kind of
repository setup, the results quite often do what the user
expects.  But this has also historically been the cause of
some poorly behaved corner cases. These cases can be hard to
find, because they happen at the conjunction of two
relatively rare circumstances:

  1. We are running some code which assumes there's a
     repository present, but there isn't necessarily one
     (e.g., low-level diff code triggered by "git diff
     --no-index" might try to look at some repository data).

  2. We have an unusual setup, like being in a subdirectory
     of the working tree, or we have a .git file (rather
     than a directory), or we are running a tool like "init"
     or "clone" which may operate on a repository in a
     different directory.

Our test scripts often cover (1), but miss doing (2) at the
same time, and so the fallback appears to work but has
lurking bugs. We can flush these bugs out by refusing to do
the fallback entirely., This makes potential problems a lot
more obvious by complaining even for "usual" setups.

This passes the test suite (after the adjustments in the
previous patches), but there's a risk of regression for any
cases where the fallback usually works fine but the code
isn't exercised by the test suite.  So by itself, this
commit is a potential step backward, but lets us take two
steps forward once we've identified and fixed any such
instances.

Signed-off-by: Jeff King <peff@peff.net>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2016-10-26 13:30:51 -07:00
2016-05-10 11:19:07 -07:00
2016-10-26 13:28:47 -07:00
2016-02-22 14:51:09 -08:00
2016-10-20 09:33:17 -07:00
2016-10-17 13:25:20 -07:00
2016-10-26 13:30:51 -07:00
2016-09-26 17:46:44 -07:00
2016-10-26 13:14:54 -07:00
2016-02-22 14:51:09 -08:00
2016-02-22 14:50:32 -08:00
2016-02-22 14:50:32 -08:00
2016-09-29 15:42:18 -07:00
2016-10-26 13:30:51 -07:00
2016-05-09 12:29:08 -07:00
2016-02-22 14:51:09 -08:00
2016-08-12 09:47:37 -07:00
2016-10-10 14:03:50 -07:00
2016-10-17 13:25:21 -07:00
2016-09-26 16:09:18 -07:00
2016-05-09 12:29:08 -07:00
2016-07-27 14:15:51 -07:00
2015-11-20 08:02:05 -05:00
2016-10-26 13:30:51 -07:00
2016-09-29 15:42:18 -07:00
2016-09-29 15:42:18 -07:00
2016-09-29 15:42:18 -07:00
2016-05-09 12:29:08 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:50 -07:00
2016-07-01 12:44:57 -07:00
2016-07-01 12:44:57 -07:00
2016-08-11 14:35:42 -07:00
2016-10-20 11:19:43 +01:00
2016-10-26 13:14:45 -07:00
2016-09-29 15:42:18 -07:00
2016-09-19 13:51:43 -07:00
2016-10-17 13:25:18 -07:00
2016-07-06 13:38:06 -07:00
2016-02-22 14:51:09 -08:00
2016-09-29 15:42:18 -07:00
2016-05-17 14:38:32 -07:00
2016-10-17 13:25:21 -07:00
2016-07-29 11:05:07 -07:00
2016-07-29 11:05:07 -07:00
2016-09-26 16:09:18 -07:00
2015-11-20 08:02:05 -05:00
2016-06-13 14:38:16 -07:00
2016-09-29 15:42:18 -07:00
2016-09-25 16:44:13 -07:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2016-10-26 13:14:45 -07:00
2016-07-28 11:26:03 -07:00
2016-07-28 11:26:03 -07:00
2016-05-09 12:29:08 -07:00
2016-10-10 14:03:46 -07:00
2015-09-25 08:54:54 -07:00
2016-10-26 13:14:45 -07:00
2016-10-10 14:03:50 -07:00
2016-10-11 14:24:02 -07:00
2016-10-10 14:03:50 -07:00
2016-04-25 15:17:15 -07:00
2016-08-19 15:34:16 -07:00
2016-07-14 15:50:41 -07:00
2016-09-29 15:42:18 -07:00
2016-10-10 14:03:46 -07:00
2016-10-10 14:03:50 -07:00
2016-07-01 15:09:10 -07:00
2016-09-25 16:44:13 -07:00
2016-09-29 15:42:18 -07:00
2016-10-17 13:25:21 -07:00
2016-08-05 09:28:17 -07:00
2016-10-17 13:25:20 -07:00
2016-10-10 14:03:50 -07:00
2016-09-29 15:42:18 -07:00
2016-09-19 13:47:18 -07:00
2016-02-22 10:40:35 -08: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 http://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 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.

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
Git with broken hash generation to generate collisions between object IDs. Don't use this!
https://undefinedbehavior.de/posts/commit-vandalism/
Readme 217 MiB
Languages
C 50%
Shell 38.2%
Perl 5.5%
Tcl 3.5%
Python 0.9%
Other 1.7%