Debian bug report logs - #1173, boring messages

Subject: Bug#1173: ircII bug? ircII.servers
Reply-To: jimr@simons-rock.edu, debian-bugs@pixar.com
Resent-From: "James A. Robinson" <jimr@simons-rock.edu>
Resent-To: debian-devel@pixar.com
Resent-Date: Mon, 31 Jul 1995 01:33:03 GMT
Resent-Message-ID: <debian-bugs-handler.1173.073101300127021@pixar.com>
Resent-Sender: iwj10@cus.cam.ac.uk
X-Debian-PR-Package: ircii
X-Debian-PR-Keywords: 
Received: via spool for debian-bugs; Mon, 31 Jul 1995 01:33:03 GMT
Received: with rfc822 via encapsulated-mail id 073101300127021;
          Mon, 31 Jul 1995 01:30:01 GMT
Received: from pixar.com by mongo.pixar.com with smtp
	(Smail3.1.28.1 #15) id m0scjf8-0003dRC; Sun, 30 Jul 95 18:28 PDT
Received: from plato.simons-rock.edu by pixar.com with SMTP id AA17838
  (5.67b/IDA-1.5 for debian-bugs-pipe@mongo.pixar.com); Sun, 30 Jul 1995 18:28:55 -0700
Received: from simons-rock.edu by plato.simons-rock.edu with smtp
	(Smail3.1.29.1 #3) id m0scjf2-000018C; Sun, 30 Jul 95 21:28 EDT
Message-Id: <m0scjf2-000018C@plato.simons-rock.edu>
X-Mailer: MH 6.8.3
To: Debian Bugs <debian-bugs@pixar.com>
Dcc:
Date: Sun, 30 Jul 1995 21:28:52 -0400
From: "James A. Robinson" <jimr@simons-rock.edu>


Package: ircii
Version: 2.8.2-1

Shouldn't ircII have an /etc/ircII.servers file, with perhaps
/usr/lib/irc/ircII.servers pointing towards it?


Jim

From: iwj10@thor.cam.ac.uk (Ian Jackson)
To: jimr@simons-rock.edu
Subject: Bug#1173: Acknowledgement (was: ircII bug? ircII.servers)
In-Reply-To: <m0scjf2-000018C@plato.simons-rock.edu>
References: <m0scjf2-000018C@plato.simons-rock.edu>

Thank you for the problem report you have sent regarding Debian GNU/Linux.
This is an automatically generated reply, to let you know your message has
been received.  It is being forwarded to the developers' mailing list for
their attention; they will reply in due course.

If you wish to submit further information on your problem, please send
it to debian-bugs@pixar.com, but please ensure that the Subject
line of your message starts with "Bug#1173" or "Re: Bug#1173" so that
we can identify it as relating to the same problem.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the bug-tracking system.

Ian Jackson
(maintainer, debian-bugs)