Annapolis, Indiana
Annapolis is an unincorporated community in Penn Township, Parke County, in the U.S. state of Indiana.[2]
Annapolis, Indiana | |
---|---|
Parke County's location in Indiana | |
Annapolis Location in Parke County | |
Coordinates: 39°51′09″N 87°15′02″W | |
Country | United States |
State | Indiana |
County | Parke |
Township | Penn |
Elevation | 646 ft (197 m) |
Time zone | UTC-5 (Eastern (EST)) |
• Summer (DST) | UTC-4 (EDT) |
ZIP code | 47832 |
Area code(s) | 765 |
GNIS feature ID | 430182 |
History
Annapolis was first settled in 1825 or 1826.[3] It was platted on February 4, 1837, by settlers William Maris, Sr., and John Moulder.[4] As of 1910, its population was about 200.[5] It was probably named after Annapolis, Maryland.[6] A post office was established at Annapolis in 1837, and remained in operation until 1905.[7]
Geography
Annapolis is located in northwestern Parke County, about 1 mile (1.6 km) north of Bloomingdale and less than one mile west of U.S. Route 41. Its elevation is 646 feet.[2]
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?
gollark: probably.
References
- "US Board on Geographic Names". United States Geological Survey. October 25, 2007. Retrieved 2017-04-16.
- "Annapolis, Indiana". Geographic Names Information System. United States Geological Survey. Retrieved 2010-11-01.
- Bowen 1913, p. 196.
- Bowen 1913, p. 52.
- Bowen 1913, p. 154.
- Baker, Ronald L.; Carmony, Marvin (1975). Indiana Place Names. Bloomington, Indiana: Indiana University Press. p. 4.
- "Parke County". Jim Forte Postal History. Retrieved 30 September 2015.
Bibliography
- History of Parke and Vermillion Counties Indiana. Indianapolis: B. F. Bowen and Company. 1913. pp. 25–225. Retrieved 2010-12-17.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.