From 23c53e3ef91c301fdbf469f0dc6df89da34b7911 Mon Sep 17 00:00:00 2001
From: Tony Cook <tony@develop-help.com>
Date: Sun, 9 Sep 2012 23:55:54 +1000
Subject: [PATCH] more thread docs

---
 lib/Imager/Threads.pod | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/lib/Imager/Threads.pod b/lib/Imager/Threads.pod
index 7defd842..a99a995a 100644
--- a/lib/Imager/Threads.pod
+++ b/lib/Imager/Threads.pod
@@ -41,8 +41,20 @@ its access to C<giflib>.
 
 =item *
 
-killing a thread reading or writing TIFF or GIF files may deadlock
-other threads when they attempt to read or write TIFF or GIF files.
+C<T1Lib>, used by one of Imager's font drivers, is not thread safe.
+C<Imager::Font::T1> works around this by single threading access.
+
+=item *
+
+killing a thread reading or writing TIFF or GIF files, or using T1
+fonts through C<Imager::Font::T1> may deadlock other threads when they
+attempt to read or write TIFF or GIF files, or work with Type 1 fonts.
+
+=item *
+
+Fill, font, color or I/O layer objects created in one thread and are
+valid for use in child threads.  If you manage to duplicate such an
+object in another thread, you get to keep both pieces when it breaks.
 
 =back
 
-- 
2.39.5