Your suggestions are good. They tell how to transfer file contents, and I also do it in similar way (when I don't have git available). The other suggestions tell how to transfer Rietveld CL metadata, so you can update same CL while working in the new working copy.
On Mon, Aug 3, 2009 at 09:55, Jeremy Orlow <[email protected]> wrote: > If I'm not on Windows, I use diff and patch. When on Windows, because I've > never been able to get any version of patch to work reliably, I sometimes > just sync the 2 repos to the same version and then simply copy the files > across. > Note that I've never tried the other suggestions, so they could easily be > superior. :-) > > J > > > On Mon, Aug 3, 2009 at 9:49 AM, Mohamed Mansour > <[email protected]>wrote: > >> Hi, >> If your source contents don't change, you can just copy the gcl_info >> directory (chrome\src\.svn\gcl_info) and it will keep the change lists >> intact. >> >> If the source contents change after your new source tree, just upload them >> to code review and fetch them back in when you got your clean tree. (you >> still need the gcl_info folder contents if you want to keep the connection >> between your cl's and rietveld) >> >> Welcome to chromium :) >> >> -- Mohamed Mansour >> >> >> >> On Thu, Jul 30, 2009 at 12:56 AM, James Su <[email protected]> wrote: >> >>> Hi, >>> I'm so happy that I just got my chromium account, and going to rebuild >>> my local source tree with writable svn repository. But I have some pending >>> CLs in my old readonly source tree, so I'm wondering is it possible to >>> migrate those CLs to a new source tree? >>> >>> Regards >>> James Su >>> >>> >>> >> >> >> > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
