From owner-freebsd-ports@FreeBSD.ORG  Tue Jun 24 16:00:43 2003
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
Delivered-To: freebsd-ports@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id E590A37B421
	for <ports@FreeBSD.org>; Tue, 24 Jun 2003 16:00:42 -0700 (PDT)
Received: from perrin.int.nxad.com (internal.ext.nxad.com [69.1.70.251])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CB1AC43FF7
	for <ports@FreeBSD.org>; Tue, 24 Jun 2003 16:00:33 -0700 (PDT)
	(envelope-from sean@nxad.com)
Received: by perrin.int.nxad.com (Postfix, from userid 1001)
	id F32B921062; Tue, 24 Jun 2003 16:00:32 -0700 (PDT)
Date: Tue, 24 Jun 2003 16:00:32 -0700
From: Sean Chittenden <sean@chittenden.org>
To: Nakal <nakal@web.de>
Message-ID: <20030624230032.GJ97131@perrin.int.nxad.com>
References: <200306242344.59552.nakal@web.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200306242344.59552.nakal@web.de>
X-PGP-Key: finger seanc@FreeBSD.org
X-PGP-Fingerprint: 3849 3760 1AFE 7B17 11A0  83A6 DD99 E31F BC84 B341
X-Web-Homepage: http://sean.chittenden.org/
User-Agent: Mutt/1.5.4i
cc: ports@FreeBSD.org
Subject: Re: FreeBSD Port: docbookide.el
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Porting software to FreeBSD <freebsd-ports.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-ports>
List-Post: <mailto:freebsd-ports@freebsd.org>
List-Help: <mailto:freebsd-ports-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-ports>,
	<mailto:freebsd-ports-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 24 Jun 2003 23:00:43 -0000

> I have found a small bug in 
> /usr/ports/textproc/docbookide.el/pkg-message.
> 
> I am not an elisp expert, but I think I fixed it, because it seems to 
> work now.

Thank you, I've committed the update.  -sc

-- 
Sean Chittenden