On Nov 1, 2012, at 21:41, Blair Zajac wrote: > Yes, but we still like to do 'svn copy' to retain history.
Sure, for files that have a history. But in the past, if I needed to, say, add a patch to both graphviz and graphviz-devel, I would have added it to one, committed it, updated, then copied it to the other and committed. Now I don't feel bad about committing both together as unrelated adds. > svn isn't like git where it'll put history together based on file contents > alone. git does that? Neat. I really need to read more of the git manual. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
