From owner-freebsd-ports@FreeBSD.ORG  Sat May 19 22:54:55 2007
Return-Path: <owner-freebsd-ports@FreeBSD.ORG>
X-Original-To: freebsd-ports@FreeBSD.org
Delivered-To: freebsd-ports@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52])
	by hub.freebsd.org (Postfix) with ESMTP id 35B2116A400
	for <freebsd-ports@FreeBSD.org>; Sat, 19 May 2007 22:54:55 +0000 (UTC)
	(envelope-from llwang@infor.ck.tp.edu.tw)
Received: from infor.ck.tp.edu.tw (infor.ck.tp.edu.tw [203.64.26.200])
	by mx1.freebsd.org (Postfix) with ESMTP id 04F4D13C465
	for <freebsd-ports@FreeBSD.org>; Sat, 19 May 2007 22:54:54 +0000 (UTC)
	(envelope-from llwang@infor.ck.tp.edu.tw)
Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001)
	id D1446171C0; Sun, 20 May 2007 06:54:53 +0800 (CST)
Date: Sun, 20 May 2007 06:54:53 +0800
From: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>
To: freebsd-ports@FreeBSD.org
Message-ID: <20070519225453.GA71768@Athena.infor.org>
Mail-Followup-To: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>,
	freebsd-ports@FreeBSD.org
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
Content-Disposition: inline
User-Agent: Mutt/1.5.15 (2007-04-06)
Cc: 
Subject: Subject=Ports tree : Xorg-7.2 release freeze, ETA?
X-BeenThere: freebsd-ports@freebsd.org
X-Mailman-Version: 2.1.5
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: Sat, 19 May 2007 22:54:55 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Talking about branching, I think we did effectively have a short-lived 
"development branch" in the git repository.  It is too painful and
inefficient to branch in the CVS, not to mention merging the branches
afterwards.  Had we have lightweight branching and merging like those
in svn / svk (I don't know about git), that short-lived development
branch could take place in the main repository.  However, IMHO, for a
large change like this, keeping the entire tree frozen for a little
while just before merging really isn't that bad an idea.

- -- llwang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.3 (FreeBSD)

iD8DBQFGT4A8CQM7t5B2mhARAtOsAJ4sgGoTABuhU14r0B8r30WvkoUj8gCcDZy1
2GWNHK92tHI5ke23LeSq9lI=
=JDI/
-----END PGP SIGNATURE-----