Utran
Utran is a census town in Surat district in the Indian state of Gujarat.
Utran | |
|---|---|
city | |
  Utran Location in Gujarat, India  Utran Utran (India) | |
| Coordinates: 21.23°N 72.87°E | |
| Country |  |
| State | Gujarat |
| District | Surat |
| Elevation | 12 m (39 ft) |
| Population (2001) | |
| • Total | 12,894 |
| Languages | |
| • Official | Gujarati, Hindi |
| Time zone | UTC+5:30 (IST) |
| Vehicle registration | GJ 5 |
| Website | gujaratindia |
Geography
Utran is located at 21.23°N 72.87°E.[1] It has an average elevation of 12 metres (39 feet).
Demographics
As of 2001 India census,[2] Utran had a population of 12,894. Males constitute 54% of the population and females 46%. Utran has an average literacy rate of 73%, higher than the national average of 59.5%: male literacy is 80%, and female literacy is 64%. In Utran, 13% of the population is under 6 years of age.
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.
gollark: UPDATE: this is wrong.
gollark: > Git uses delta encoding to store some of the objects in packfiles. However, you don't want to have to play back every single change ever on a given file in order to get the current version, so Git also has occasional snapshots of the file contents stored as well. "Resolving deltas" is the step that deals with making sure all of that stays consistent.
gollark: A lot?
See also
References
- Falling Rain Genomics, Inc - Utran
- "Census of India 2001: Data from the 2001 Census, including cities, villages and towns (Provisional)". Census Commission of India. Archived from the original on 16 June 2004. Retrieved 1 November 2008.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.