Jeff King 087b6d5840 sha1_file: always allow relative paths to alternates
We recursively expand alternates repositories, so that if A
borrows from B which borrows from C, A can see all objects.

For the root object database, we allow relative paths, so A
can point to B as "../B/objects". However, we currently do
not allow relative paths when recursing, so B must use an
absolute path to reach C.

That is an ancient protection from c2f493a (Transitively
read alternatives, 2006-05-07) that tries to avoid adding
the same alternate through two different paths. Since
5bdf0a8 (sha1_file: normalize alt_odb path before comparing
and storing, 2011-09-07), we use a normalized absolute path
for each alt_odb entry.

This means that in most cases the protection is no longer
necessary; we will detect the duplicate no matter how we got
there (but see below).  And it's a good idea to get rid of
it, as it creates an unnecessary complication when setting
up recursive alternates (B has to know that A is going to
borrow from it and make sure to use an absolute path).

Note that our normalization doesn't actually look at the
filesystem, so it can still be fooled by crossing symbolic
links. But that's also true of absolute paths, so it's not a
good reason to disallow only relative paths (it's
potentially a reason to switch to real_path(), but that's a
separate and non-trivial change).

We adjust the test script here to demonstrate that this now
works, and add new tests to show that the normalization does
indeed suppress duplicates.

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