moving sctp to a separate directory ? (Re: svn commit: r201523 - head/sys/netinet)

[Robert Watson]

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.

This is simply not the case.  It's easy to rename in the parent branch, but 
that rename is propagated poorly to children branches, where developers will 
have to manually reconstruct changes made to the old file and apply them by 
hand to the new file.  It's even worse when things are propagated from one 
repository to another, as all of our downstream vendors do, importing them 
into some vast combination of {CVS, SVN, P4, git, ..}.  Why create unnecessary 
work for everyone?

Robert N M Watson
Computer Laboratory
University of Cambridge