FYI here was the commit that removed it, by Tyler:

http://svn.apache.org/viewvc?view=revision&revision=1645371


++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Chris Mattmann, Ph.D.
Chief Architect
Instrument Software and Science Data Systems Section (398)
NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
Office: 168-519, Mailstop: 168-527
Email: [email protected]
WWW:  http://sunset.usc.edu/~mattmann/
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
Adjunct Associate Professor, Computer Science Department
University of Southern California, Los Angeles, CA 90089 USA
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++






-----Original Message-----
From: <Mattmann>, Chris Mattmann <[email protected]>
Reply-To: "[email protected]" <[email protected]>
Date: Wednesday, May 20, 2015 at 1:39 PM
To: "[email protected]" <[email protected]>
Subject: Any reason we removed the links to other downstream Tika APIs off
the main web site?

>Hey Folks,
>
>Before, we had links in the description of Tika that Tyler put in
>that included links to e.g., Tika Python and other downstream APIs.
>Would there be objection to putting those links back up, they
>seemed to have been removed? I created a wiki page on our Tika
>wiki with links to downstream API bindings. I would like to add
>the text back in, and then e.g., link to that wiki page. That
>OK?
>
>If I don’t hear objections in the next day or so I will add the
>link back in.
>
>Cheers,
>Chris
>
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Chris Mattmann, Ph.D.
>Chief Architect
>Instrument Software and Science Data Systems Section (398)
>NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
>Office: 168-519, Mailstop: 168-527
>Email: [email protected]
>WWW:  http://sunset.usc.edu/~mattmann/
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>Adjunct Associate Professor, Computer Science Department
>University of Southern California, Los Angeles, CA 90089 USA
>++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
>
>
>
>

Reply via email to