Date: Fri, 5 Mar 2010 13:21:33 +0000 (GMT) From: Robert Watson <rwatson@FreeBSD.org> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: freebsd-current@FreeBSD.org, paradox <ddkprog@yahoo.com> Subject: Re: propose: all arch move into a separate dir Message-ID: <alpine.BSF.2.00.1003051320050.5181@fledge.watson.org> In-Reply-To: <3699.1267782245@critter.freebsd.dk> References: <3699.1267782245@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 5 Mar 2010, Poul-Henning Kamp wrote: > In message <alpine.BSF.2.00.1003050940290.5181@fledge.watson.org>, Robert > Watso n writes: > >> [...] it's that changes in layout come with a less visible but much larger >> cost than "svn mv". > > Really stupid question: Doesn't svn support symlinks ? Yes, but does that help? The issue is not user applications that can't find their header files, it's people who maintain patchsets in revision control systems, such as svn, Perforce, git, etc, whose work will be derailed when automatic merging fails. As I said, I've run into this with the TrustedBSD work several times: someone rearranges files in the network stack or VFS and you're left trying to figure out where the code moved, how to re-apply your changes, whether you've missed anything, etc. Continuity over time in code location makes that task orders of magnitude easier, and costs the project little. Robert N M Watson Computer Laboratory University of Cambridge
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?alpine.BSF.2.00.1003051320050.5181>