[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

tin uploaded



-----BEGIN PGP SIGNED MESSAGE-----

Date: 24 Apr 96 20:18 UT
Format: 1.4
Distribution: Development
Priority: Low
Maintainer: Kenny Wickstrom <kenny@kennet.com>
Source: tin
Binary: tin
Architecture: i386 source
Version: 1.3beta.950824-11
Description: 
 tin: Threaded Internet News reader
 -  It has a powerful full screen text mode user interface, where
 -  most actions are available at the press of a single key.  It is
 -  highly configurable.
 -  .
 -  tin can read news from a news server via NNTP (the Network News Transfer 
 -  Protocol) or from the local host (/var/spool/news).  You must have either
 -  a news server available - large sites usually provide a site-wide server, 
 -  or the articles local on the host in /var/spool/news.
 -  .
 -  Note: If you read news from the local host, you will need to provide the
 -  executable /usr/bin/inews.  This can be found in the package 
 -  news/inewsinn-xxx (if this is still available).
 -  .
 -  If you install a news server on your system (either containing
 -  just local newsgroups or with a partial or full USENET feed) you
 -  can configure tin to access it.
Changes: 
 04/15/96 Kenny Wickstrom <kenny@kennet.com>
        * These comments refer to tin-1.3beta.950824-11
        * debian.rules: Changed debian=11
        * debian.control: changed (really did add mail-transport-agent & inews)
             recommends: smail | sendmail | mail-transport-agent
             suggests: inn | inewsinn | inews
Files:
 99f0d56f67c4e8cd576485a9abea49e0  615807  news  tin-1.3beta.950824-11.tar.gz
 b616a12b09c32156e527daed9a7aa78d  8983  news  tin-1.3beta.950824-11.diff.gz
 154bc12e5fb8915c8d0765ae9d99d476  413041  news  tin-1.3beta.950824-11.i386.deb

-----BEGIN PGP SIGNATURE-----
Version: 2.6.2

iQB1AwUBMYWlk+cA9UBUFUvpAQHvKgL9HGNxQylrM1Wvat/jMZK27cRSF+6Tq+Dk
6nnr9mJ9a1yZkhgulW8W8Z13dbcn0j4HogiiFXVCIpE3LoZi7Vx2SAh0doY3ZlKn
uyD6EZRxbFJDINP0wZzznZWJjZ44zW6u
=n644
-----END PGP SIGNATURE-----


Reply to: