Date: Fri, 14 Dec 2001 20:43:08 +0900 From: Jun Kuriyama <kuriyama@imgsrc.co.jp> To: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: ports/comms Makefile ports/comms/conserver-com Makefile distinfo pkg-comment pkg-descr pkg-plist ports/comms/conserver-com/files patch-conserver.rc Message-ID: <7mk7vqauyb.wl@waterblue.imgsrc.co.jp> In-Reply-To: <20011210005040.Q23826@squall.waterspout.com> References: <200112091440.fB9EeD726698@freefall.freebsd.org> <20011209134457.A23826@squall.waterspout.com> <7melm4doju.wl@waterblue.imgsrc.co.jp> <20011210005040.Q23826@squall.waterspout.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At Mon, 10 Dec 2001 00:50:40 -0500, Will Andrews wrote: > > Hmm, this conserver is forked from 5.21-Beta version of conserver. > > Our comms/conserver is imported at 5.21-Beta so I think > > comms/conserver and comms/conserver-com are very different program. > > Doesn't matter if they were forked a long time ago. If they are > even mildly related, the port must be repocopied. Does this need > to be made clear in the Committers' Handbook? Hmm. Until now, I supposed why repocopy is required is to keep history. The history of this conserver-com itself is not shared with conserver's one in the period after conserver is ported to the FreeBSD's Ports Collection. Anyway, I appreciate if you clarify "when we should repocopy". -- Jun Kuriyama <kuriyama@imgsrc.co.jp> // IMG SRC, Inc. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?7mk7vqauyb.wl>