Thank you for correcting the text in this article. Your corrections improve Papers Past searches for everyone. See the latest corrections.

This article contains searchable text which was automatically generated and may contain errors. Join the community and correct any errors you spot to help us improve Papers Past.

Article image
Article image
Article image
Article image

PLUNKET SHIELD DATES

[Tib Dotted Press Association.} CHRISTCHURCH. October 22. At a meeting of the Canterbury Cricket Association Plunket Shield dates were discussed. It was decided that the dates for the Otago match be February 28, March 1,3, and 4. The Chairman said that Canterbury had suggested that the dates for the Auckland match be January 3,4, 6, and 7. Auckland desired the match to be started on January 2. However, those dates would not fit in with those suggested for the Wellington match. Mr Dey said that they should reply to Auckland, stating that the dates as suggested by Canterbury were the only ones suitable, hut should the Wellington match finish in three days the Auckland match could commence on January 2, as suggested by Auckland. He moved in that direction, and the motion was carried. It was decided that the dates for the Wellington match he December 28. 30, 31, and January 1.

Permanent link to this item

https://paperspast.natlib.govt.nz/newspapers/ESD19291022.2.21.15

Bibliographic details

Evening Star, Issue 20312, 22 October 1929, Page 4

Word Count
155

PLUNKET SHIELD DATES Evening Star, Issue 20312, 22 October 1929, Page 4

PLUNKET SHIELD DATES Evening Star, Issue 20312, 22 October 1929, Page 4

Help

Log in or create a Papers Past website account

Use your Papers Past website account to correct newspaper text.

By creating and using this account you agree to our terms of use.

Log in with RealMe®

If you’ve used a RealMe login somewhere else, you can use it here too. If you don’t already have a username and password, just click Log in and you can choose to create one.


Log in again to continue your work

Your session has expired.

Log in again with RealMe®


Alert