MIME-Version: 1.0
In-Reply-To: <rt-3.8.6-2877-1353591025-1514.31940-0-0@isc.org>
X-Mailer: MIME-tools 5.505 (Entity 5.505)
Content-Disposition: inline
X-RT-Interface: Web
References: <RT-Ticket-31940@isc.org>
 <50AE17E00200006D00037565@soto.provo.novell.com>
 <50ADB92D.2060901@isc.org> <rt-3.8.6-2877-1353586225-30.31940-5-0@isc.org>
 <50AE99570200006D00037610@soto.provo.novell.com>
 <rt-3.8.6-2877-1353591025-1514.31940-0-0@isc.org>
Content-Type: text/plain; charset="utf-8"
Message-ID: <rt-4.2.8-34065-1487691847-473.31940-0-0@isc.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
RT-Send-CC:
X-RT-Encrypt: 0
X-RT-Sign: 0
Content-Length: 526

Dear Wei:

You will be pleased to hear that we have finally addressed this issue in our upcoming releases 4.3.6 adn 4.1-ESV-R15 both due out in May '17, as well as in 4.4.0 whose date is TDB.  You were among others who submitted patches for this.

Thank you for your support and interest in our software and for taking the time to submit a patch.  If you care to be recognized in our release notes for your contribution please respond with how you care to be identified.

Sincerely,

Thomas Markwalder
ISC Software Engineering