Buddleja parviflora

Buddleja parviflora is large dioecious shrub or small tree endemic to much of upland Mexico north of the Isthmus of Tehuantepec, in forests at elevations of 750 – 3500 m. The species was first named and described by Kunth in 1818.[1][2]

Buddleja parviflora
Scientific classification
Kingdom: Plantae
Clade: Tracheophytes
Clade: Angiosperms
Clade: Eudicots
Clade: Asterids
Order: Lamiales
Family: Scrophulariaceae
Genus: Buddleja
Species:
B. parviflora
Binomial name
Buddleja parviflora
Synonyms
  • Buddleja abbreviata Kunth
  • Buddleja brevifolia Willd. ex Schultes & Schultes
  • Buddleja gracilis Kunth
  • Buddleja intermedia Kunth
  • Buddleja lanceolata Benth.
  • Buddleja ligustrina Loes.
  • Buddleja microphylla Kunth
  • Buddleja monticola Loes.
  • Buddleja obtusifolia Martens & Galeotti
  • Buddleja venusta Kunth

Description

Buddleja parviflora grows to a height of <10 m in the wild, with a trunk < 20 cm in diameter; the bark blackish and exfoliating. The young branches are subquadrangular and tomentose, bearing opposite subcoriaceous leaves of variable shape, 3 – 12 cm long by 1 – 4.5 cm wide. The white to greenish-white inflorescences are paniculate, 3 – 18 cm long by 2 – 12 cm comprising 2 – 3 orders of branches subtended by small leaves and bearing small cymules with 3 – 5 tiny flowers, the campanulate corollas 1 – 1.5 mm long. Ploidy: 2n = 76.[2]

Cultivation

The species is uncommon in cultivation. Hardiness: USDA zones 8–9.[3]

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.

References
  1. Kunth, in Humboldt, Bonpland, and Kunth. (1818). Nov. gen. sp., ed. fol. 2:284, ed. quar. 2:353
  2. Norman, E. M. (2000). Buddlejaceae. Flora Neotropica 81, pp. 135 - 141. New York Botanical Garden, USA
  3. Stuart, D. (2006). Buddlejas. Plant Collector Guide. Timber Press, Oregon, USA. ISBN 978-0-88192-688-0
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.