215th Infantry Division (German Empire)
The 215th Infantry Division (German: 215. Infanterie-Division) was a unit in the German Imperial Army during World War I. Created in September 1916, it primarily saw service on the Eastern Front and in Ukraine.
| 215th Infantry Division (215. Infanterie-Division) | |
|---|---|
| Active | 1916–19 |
| Country | German Empire |
| Branch | Army |
| Type | Infantry |
| Size | Approx. 15,000 |
| Engagements | World War I
|
Order of battle (May 1918)
- 61. Reserve-Infanterie-Brigade
- Reserve-Ersatz-Regiment Nr. 2
- Landwehr-Infanterie-Regiment Nr. 71
- Reserve-Infanterie-Regiment Nr. 224
- 3. Eskadron/Reserve-Husaren-Regiment Nr. 8
- Artillerie-Kommandeur Nr. 215
- Feldartillerie-Regiment Nr. 274
- Division-Nachrichtung-Kommandeur Nr. 215
Chronology
1916
- 15 September–17 September – In reserve behind Armee-Abteilung A in France
- 18 September–2 November – Frontline service in Champagne
- 2–8 November – Transported to the Eastern Front
- 8 November–31 December – Frontline service on Upper Styr and Stochod rivers
1917
- 1 January–1 December – Frontline service on Upper Styr and Stochod rivers
- 2 December–17 December – Ceasefire on Eastern Front
- 18 December–31 December – Armistice on Eastern Front
1918
- 1 January–18 February – Armistice on Eastern Front
- 18 February–21 June – Service in Ukraine
- 22 June – 5 November – Occupation of Ukraine
- 16 November–31 December – Withdrawal from Ukraine
1919
- 1 January–16 March – Withdrawal from Ukraine
Sources
gollark: I don't THINK so.
gollark: PETA will destroy you.
gollark: At least it has generics.
gollark: Oh, and it's not a special case as much as just annoying, but it's a compile error to not use a variable or import. Which I would find reasonable as a linter rule, but it makes quickly editing and testing bits of code more annoying.
gollark: As well as having special casing for stuff, it often is just pointlessly hostile to abstracting anything:- lol no generics- you literally cannot define a well-typed `min`/`max` function (like Lua has). Unless you do something weird like... implement an interface for that on all the builtin number types, and I don't know if it would let you do that.- no map/filter/reduce stuff- `if err != nil { return err }`- the recommended way to map over an array in parallel, if I remember right, is to run a goroutine for every element which does whatever task you want then adds the result to a shared "output" array, and use a WaitGroup thingy to wait for all the goroutines. This is a lot of boilerplate.
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.