Hi Tim. So long that users need not upgrade their SVN clients, i see no problem with having the repository going to 1.5. Talking about that have people give SVK a try? SVK can check out code from SVN repositories, and, IIRC, supports the same "merge without out indicating the previous merge revision" feature. Eric
2008/7/29, Tim Schaub <[EMAIL PROTECTED]>: > Hey- > > Wondering if others think a move to subversion 1.5 would be good. > > A few features would be nice for OL development. Particularly merge > tracking. From the release notes: > > """ > Merging changes from (say) trunk to a branch no longer requires that you > specify the revision range. Instead, each time you want to sync up with > trunk, you can just do: > > $ cd BRANCH_WORKING_COPY > $ svn merge URL_TO_TRUNK > > Subversion will figure out what changes from URL_TO_TRUNK have not yet > been merged and pull in just those changes. When it's time to merge the > branch back to trunk, do this: > > $ cd TRUNK_WORKING_COPY > $ svn merge --reintegrate URL_TO_BRANCH > """ > > http://subversion.tigris.org/svn_1.5_releasenotes.html#merge-tracking > > Pretty nice for sandbox users. Not sure if there are constraints on > doing this on the MC side. > > Tim > > PS - One (perhaps very minor) change that may affect some is that the > repository basename is displayed in XML and HTML index views. This > breaks anything that previously relied on titles that were only revision > numbers (zc.buildout recipes break). > _______________________________________________ > Dev mailing list > [email protected] > http://openlayers.org/mailman/listinfo/dev > _______________________________________________ Dev mailing list [email protected] http://openlayers.org/mailman/listinfo/dev
