From owner-freebsd-ports@FreeBSD.ORG Tue Nov 1 14:40:23 2005 Return-Path: X-Original-To: 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 4BC7016A41F; Tue, 1 Nov 2005 14:40:23 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from jengal.datamax.bg (jengal.datamax.bg [82.103.104.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id D291A43D45; Tue, 1 Nov 2005 14:40:22 +0000 (GMT) (envelope-from vd@datamax.bg) Received: from qlovarnika.bg.datamax (qlovarnika.bg.datamax [192.168.10.2]) by jengal.datamax.bg (Postfix) with SMTP id 8D994B855; Tue, 1 Nov 2005 16:40:21 +0200 (EET) Received: (nullmailer pid 52037 invoked by uid 1002); Tue, 01 Nov 2005 14:40:21 -0000 Date: Tue, 1 Nov 2005 16:40:21 +0200 From: Vasil Dimov To: freebsd-ports@freebsd.org Message-ID: <20051101144021.GA51973@qlovarnika.bg.datamax> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="FL5UXtIhxfXey3p5" Content-Disposition: inline X-OS: FreeBSD 6.0-RC1 User-Agent: Mutt/1.5.11 Cc: Peter Schuller , lawrance@freebsd.org, Steve Clement Subject: rdiff-backup development branch forked again X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: vd@datamax.bg List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 01 Nov 2005 14:40:23 -0000 --FL5UXtIhxfXey3p5 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi, It seems that rdiff-backup development branch has been forked again: http://www.nongnu.org/rdiff-backup/ Just to remind you that some time ago we deleted rdiff-backup-devel port, as there was no development branch at that time. Now it is time to (re)create it, based on rdiff-backup version 1.1.0. Peter, Steve does someone of you want to maintain the "new" rdiff-backup-devel port? If noone submits it in a week or so, then I will do it. --FL5UXtIhxfXey3p5 Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- iD8DBQFDZ35TFw6SP/bBpCARArtlAJ4qoeZpfODfgCi7IB1AvDC7ZV9m+ACgrGJY 78Ei6RVwXsKJ9bOkr9svAdg= =GOV9 -----END PGP SIGNATURE----- --FL5UXtIhxfXey3p5--