10.02.2013 Views

Resource Book on Horticulture Nursery Management

Resource Book on Horticulture Nursery Management

Resource Book on Horticulture Nursery Management

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Securing the Bud with Polythene Bud and stock Joint<br />

Securing the Bud: Pull the cut together by winding a 10 to 12 cm l<strong>on</strong>g polythene<br />

strip around the stem to hold the flaps tightly over the bud shield and prevent drying.<br />

Secure the polythene strip by overlapping all windings and tucking the end under the last<br />

turn. Do not cover the bud.<br />

(B) Chip Budding<br />

Chip budding is a technique that may be used whenever mature buds are available.<br />

Because the bark does not have to "slip," the chip-budding seas<strong>on</strong> is l<strong>on</strong>ger than the Tbudding<br />

seas<strong>on</strong>. Species whose bark does not slip easily without tearing may be<br />

propagated more successfully by chip budding than by T-budding.<br />

Preparing the Stock and the Sci<strong>on</strong> Bud: Although all the basics in handling bud<br />

wood and stock are the same for chip budding and T budding, the cuts made in chip<br />

budding differ radically. The first cut <strong>on</strong> both stock and sci<strong>on</strong> is made at a 45 o to 60 o<br />

downward angle to a depth of about 3 mm. After making this cut <strong>on</strong> a smooth part of the<br />

rootstock, start the sec<strong>on</strong>d cut about 2 cm higher and draw the knife down to meet the<br />

first cut. Then remove the chip.<br />

Removing the Chip<br />

<str<strong>on</strong>g>Resource</str<strong>on</strong>g> <str<strong>on</strong>g>Book</str<strong>on</strong>g> <strong>on</strong> <strong>Horticulture</strong> <strong>Nursery</strong> <strong>Management</strong> : 29

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!