Date: Tue, 5 Jan 2010 11:43:06 +0000 (UTC) From: "Bjoern A. Zeeb" <bz@FreeBSD.org> To: Luigi Rizzo <rizzo@iet.unipi.it> Cc: svn-src-head@freebsd.org, svn-src-all@freebsd.org, src-committers@freebsd.org Subject: Re: moving sctp to a separate directory ? (Re: svn commit: r201523 - head/sys/netinet) Message-ID: <20100105114047.I88477@maildrop.int.zabbadoz.net> In-Reply-To: <20100104222323.GA49068@onelab2.iet.unipi.it> References: <201001041825.o04IPcXb043347@svn.freebsd.org> <20100104190024.GA47532@onelab2.iet.unipi.it> <517EF225-7EEB-4844-A0AD-019AD72F9403@freebsd.org> <20100104222323.GA49068@onelab2.iet.unipi.it>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 4 Jan 2010, Luigi Rizzo wrote: > I also think that the name of the new directory or the exact percentage of > ipv4-ness or netinet-ness of the sctp* and tcp* and multicast* stuff > is irrelevant. Moving directories with svn is so easy that we should not > worry even if we need a couple of attempts to find a good name. While moving in SVN is easy we still export to CVS and have a lot (most) of our users on that. Further a move will imho result in a delete and add by the exporter so there'll be a loss in file history there. Also moving it around often will put us into #include <> hell evenetually for everything that is "local" to files rather than a public interface at a well defined place which we'll need to be very carefull of anyway. /bz -- Bjoern A. Zeeb It will not break if you know what you are doing.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20100105114047.I88477>