1992 Peruvian Segunda División

The 1992 Segunda División Peruana, the second division of Peruvian football (soccer), was played by 12 teams. the tournament winner, Unión Huaral was promoted to the Torneo Zonal's Final Group. The tournament was played on a home-and-away round-robin basis.

Segunda División Peruana
Season1992
ChampionsUnión Huaral
RelegatedInternazionale
Puerto Aéreo
← 1991
1993 →

Results

Standings
Pos Team Pld W D L GF GA GD Pts Qualification or relegation
1 Unión Huaral 22 14 8 0 43 13 +30 36 Torneo Zonal - Final Group
2 Defensor Kiwi–Ciclista Lima 22 14 6 2 42 15 +27 34
3 Guardia Republicana 22 11 8 3 28 13 +15 30
4 Deportivo Zuñiga 22 12 3 7 27 18 +9 27
5 Bella Esperanza 22 9 8 5 30 19 +11 26
6 AELU 22 8 7 7 31 26 +5 23
7 Enrique Lau Chun 22 8 6 8 28 26 +2 22
8 Meteor–Lawn Tennis 22 7 8 7 27 27 0 22
9 Alcides Vigo 22 7 6 9 28 36 −8 20
10 Octavio Espinosa 22 6 2 14 21 40 −19 14
11 Puerto Aéreo 22 2 6 14 19 47 −28 10 1993 Copa Perú
12 Internazionale 22 0 0 22 0 44 −44 0
Source:
gollark: This is why you should use osmarks.tk osmarksbrowser.
gollark: Try NodeOS!
gollark: Or Great Information Transfer.
gollark: Git stands for GIT Is Tremendous.
gollark: The stages of git clone are: Receive a "pack" file of all the objects in the repo database Create an index file for the received pack Check out the head revision (for a non-bare repo, obviously)"Resolving deltas" is the message shown for the second stage, indexing the pack file ("git index-pack").Pack files do not have the actual object IDs in them, only the object content. So to determine what the object IDs are, git has to do a decompress+SHA1 of each object in the pack to produce the object ID, which is then written into the index file.An object in a pack file may be stored as a delta i.e. a sequence of changes to make to some other object. In this case, git needs to retrieve the base object, apply the commands and SHA1 the result. The base object itself might have to be derived by applying a sequence of delta commands. (Even though in the case of a clone, the base object will have been encountered already, there is a limit to how many manufactured objects are cached in memory).In summary, the "resolving deltas" stage involves decompressing and checksumming the entire repo database, which not surprisingly takes quite a long time. Presumably decompressing and calculating SHA1s actually takes more time than applying the delta commands.In the case of a subsequent fetch, the received pack file may contain references (as delta object bases) to other objects that the receiving git is expected to already have. In this case, the receiving git actually rewrites the received pack file to include any such referenced objects, so that any stored pack file is self-sufficient. This might be where the message "resolving deltas" originated.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.