Status messages from [email protected]

--===============0643906459==
Content-Type: multipart/alternative; boundary=e89a8f839e9301fc4004e0c3d6c3

--e89a8f839e9301fc4004e0c3d6c3
Content-Type: text/plain; charset=UTF-8

While reviewing held messages for the image-sig list, I came across a bunch
which seemed to be test failure/recovery status messages from
[email protected].  They look to be related to Pillow.  Here's an
example:

Build Update for python-imaging/Pillow
-------------------------------------

Build: #392
Status: Broken

Duration: 52 seconds
Commit: fd29e70 (master)
Author: Alex Clark
Message: Apply @Arfrever patch, fixes #258

View the changeset:
https://github.com/python-imaging/Pillow/compare/54cb132b8303...fd29e707e967

View the full build log and details:
https://travis-ci.org/python-imaging/Pillow/builds/8591059

...

I can't imagine that these sorts of automated messages should be going to
this list, but am happy to be proven wrong. If the list members decided
they want these messages, I can set things up so they sail through. Please
let me know what I should do with these messages now, and in the future.

Skip Montanaro
PIL moderator in /F's absence

--e89a8f839e9301fc4004e0c3d6c3
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<font face=3D"courier new, monospace">While reviewing held messages for the=
 image-sig list, I came across a bunch which seemed to be test failure/reco=
very status messages from <a href=3D"mailto:[email protected]">no=
[email protected]</a>. =C2=A0They look to be related to Pillow. =C2=
=A0Here&#39;s an example:</font><div>
<font face=3D"courier new, monospace"><br></font></div><div><font face=3D"c=
ourier new, monospace"><div>Build Update for python-imaging/Pillow</div><di=
v>-------------------------------------</div><div><br></div><div>Build: #39=
2</div>
<div>Status: Broken</div><div><br></div><div>Duration: 52 seconds</div><div=
>Commit: fd29e70 (master)</div><div>Author: Alex Clark</div><div>Message: A=
pply @Arfrever patch, fixes #258</div><div><br></div><div>View the changese=
t: <a href=3D"https://github.com/python-imaging/Pillow/compare/54cb132b8303=
...fd29e707e967">https://github.com/python-imaging/Pillow/compare/54cb132b8=
303...fd29e707e967</a></div>
<div><br></div><div>View the full build log and details: <a href=3D"https:/=
/travis-ci.org/python-imaging/Pillow/builds/8591059">https://travis-ci.org/=
python-imaging/Pillow/builds/8591059</a></div><div><br></div><div>...</div>
<div><br></div><div>I can&#39;t imagine that these sorts of automated messa=
ges should be going to this list, but am happy to be proven wrong. If the l=
ist members decided they want these messages, I can set things up so they s=
ail through. Please let me know what I should do with these messages now, a=
nd in the future.</div>
<div><br></div><div>Skip Montanaro</div><div>PIL moderator in /F&#39;s abse=
nce</div><div><br></div><div><br></div></font></div>

--e89a8f839e9301fc4004e0c3d6c3--

--===============0643906459==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Image-SIG maillist  -  [email protected]
http://mail.python.org/mailman/listinfo/image-sig

--===============0643906459==--