No subject

Thu Jun 10 09:36:35 2004
Return-Path: mjh@cs.ucl.ac.uk
Delivery-Date: Thu, 10 Jun 2004 01:36:39 -0700
Received: from wyvern.icir.org (wyvern.icir.org [192.150.187.14])
	by tigger.icir.org (8.12.9p1/8.12.8) with ESMTP id i5A8adNG053580
	for <atanu@tigger.icir.org>; Thu, 10 Jun 2004 01:36:39 -0700 (PDT)
	(envelope-from mjh@cs.ucl.ac.uk)
Received: from fruitcake.icsi.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11])
	by wyvern.icir.org (8.12.9p1/8.12.8) with ESMTP id i5A8acCJ003701
	for <atanu@icir.org>; Thu, 10 Jun 2004 01:36:38 -0700 (PDT)
	(envelope-from mjh@cs.ucl.ac.uk)
Received: from aardvark.cs.ucl.ac.uk (aardvark.cs.ucl.ac.uk [128.16.11.150])
	by fruitcake.icsi.Berkeley.EDU (8.12.10/8.12.9) with ESMTP id i5A8acEj020226
	for <atanu@icsi.berkeley.edu>; Thu, 10 Jun 2004 01:36:38 -0700 (PDT)
Received: from aardvark.cs.ucl.ac.uk (localhost [127.0.0.1])
	by aardvark.cs.ucl.ac.uk (8.12.9p2/8.12.8) with ESMTP id i5A8aZxF001683;
	Thu, 10 Jun 2004 09:36:35 +0100 (BST)
	(envelope-from mjh@aardvark.cs.ucl.ac.uk)
From: Mark Handley <M.Handley@cs.ucl.ac.uk>
X-Organisation: UCL
To: atanu@ICSI.Berkeley.EDU
cc: xorp-cvs@icir.org
Subject: Re: [Xorp-cvs] XORP cvs commit: xorp/bgp/tools/ print_peer.cc print_routes.cc print_routes.hh 
In-reply-to: Your message of "Wed, 09 Jun 2004 09:47:40 PDT."
             <48293.1086799660@tigger.icir.org> 
Date: Thu, 10 Jun 2004 09:36:35 +0100
Message-ID: <1682.1086856595@aardvark.cs.ucl.ac.uk>
Sender: mjh@cs.ucl.ac.uk


>>>>>> "Mark" == Mark Handley <M.Handley@cs.ucl.ac.uk> writes:
>
>    >> While we are here lose the two extra newlines that are printed by
>    >> the print routes and print peers commands.
>
>    Mark> BTW, those two extra newlines mark the end of the MIME header
>    Mark> :-)
>
>    Mark> The intent was to allow more than just ASCII encodings, with a
>    Mark> default to text/plain.
>
>Is this convention being followed by other external programs? If the
>xorpsh understood the newlines shouldn't it be eating them? Should I put
>them back?

Don't put them back for now.  If/when we go down this track properly,
and add proper MIME support to xorpsh, we can trivially add them back.

>This is where comments in code really come into their own!

Yup - my bad.

 - Mark