Ditto Ryan's reply. That said, I think SVN is actually OK for what MacPorts needs. I greatly prefer GIT for actual software development, because of the cloning, committing, branching, splitting, merging it provides (offline or online, parts or whole, lots of usable options). I use SVN for the MP trunk, then when working out patches I'll use GIT on the "work" directory to keep track of my changes. I find that mixing works quite well. All of that said, I would not complain if we moved to just using GIT for everything. Having lived through CVS from 10 years ago and prior, I think in comparison SVN is amazing and GIT is almost magic :) - MLD
On Mon, Jan 4, 2016, at 04:10 PM, Clemens Lang wrote: > On Fri, Jan 01, 2016 at 11:43:17PM -0600, Ryan Schmidt wrote: > > How do you commit to the MacPorts Subversion repository? > > > > Using a Subversion working copy and "svn commit"? > > This. > > > Using a Git clone and git-svn? > > Some other method? > > > > Do you have any complaints about that method or are you happy with it? > > It is slow, and it's hard to split changes or do partial commits. _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/listinfo/macports-dev
