>whew< FINALLY this is done. It took only perhaps barely 40 mins to make the modifications locally but then 5+ hours to commit all the changes. Due to repeated timeout errors from SF, it was impossible to commit all these changes as a single atomic changeset. After 10+ attempts to do so, I finally gave up and just started to commit the changes in smaller batches of 10-20 folders each. After about 20+ separate commits, all of the changes have now been properly committed to the SVN repo.
Don't wanna have to EVER do that again...! :) Steve Bohlen [email protected] http://blog.unhandled-exceptions.com http://twitter.com/sbohlen On Sun, Aug 21, 2011 at 7:14 PM, Stephen Bohlen <[email protected]> wrote: > Please be advised that this work is all done (locally, at least!) and as > soon as SF stops repeatedly timing out during my commit of all of the > changes, it will all be up there in the SF repo as planned/discussed. I'm > on commit attempt number 12 at this point, so no promises when this will > actually be 'complete' but right about now I'd give my right arm for a > non-atomic commit model in SVN that would let me resume where the prior > failed commit left off/timed out so I'd not need to keep starting again from > zero~! :P > > > Steve Bohlen > [email protected] > http://blog.unhandled-exceptions.com > http://twitter.com/sbohlen > > > On Sun, Aug 21, 2011 at 9:26 AM, Stephen Bohlen <[email protected]> wrote: > >> LOL -- well, *that* would work too, of course :) >> >> >> Steve Bohlen >> [email protected] >> http://blog.unhandled-exceptions.com >> http://twitter.com/sbohlen >> >> >> On Sun, Aug 21, 2011 at 9:25 AM, Diego Mijelshon >> <[email protected]>wrote: >> >>> Just compile and run the following program in the repo root: >>> >>> -------------------------------------- >>> >>> using System;using System.IO;class Program >>> { >>> static void Main() >>> { >>> foreach (var fileName in >>> Directory.EnumerateFiles(Environment.CurrentDirectory, "*.cs", >>> SearchOption.AllDirectories)) >>> File.WriteAllText(fileName, "//YOU ARE SEEING AN OUTDATED >>> VERSION OF THIS FILE\n//The new NHibernate repository can be found at >>> https://github.com/nhibernate/nhibernate-core\n"; + >>> File.ReadAllText(fileName)); >>> } >>> } >>> >>> -------------------------------------- >>> >>> Diego >>> >>> >>> >>> On Sun, Aug 21, 2011 at 09:39, sbohlen <[email protected]> wrote: >>> >>>> All: >>>> >>>> Looping back to this part in the thread so as to reach an actual >>>> official conclusion, my estimation of the 'voting' here is that github has >>>> rec'd the preponderance of the votes thus far and that the evil red-colored >>>> part of the graph displayed here >>>> https://nhibernate.jira.com/browse/NHsuggests strongly that the project >>>> would be best-served by our simply making >>>> a choice and moving to return to resolving open issues ASAP :) >>>> >>>> Unless anyone offers a compelling reason NOT to do this, I will proceed >>>> as follows as of 5pm ET (GMT-5) today (SUN 8/21): >>>> >>>> - adopt the github repo as our authoritative repository >>>> - commit a changeset to the SVN repo that removes the csproj, sln, >>>> binary refs, build scripts, etc., etc. (basically all but the .cs and >>>> related .xml files used in tests that someone might have linked to, >>>> etc.) >>>> and adds a OBSOLETE_REPOSITORY_DO_NOT_USE.txt to each and every folder >>>> in >>>> the tree >>>> >>>> If someone has a clever tool to do the other step of inserting the >>>> following comment as the first few lines in every .cs file... >>>> >>>> >>>> >>>> //YOU ARE SEEING AN OUTDATED VERSION OF THIS FILE >>>> //The new NHibernate repository can be found at https://github.com/** >>>> nhibernate/nhibernate-core<https://github.com/nhibernate/nhibernate-core> >>>> >>>> ...then I would encourage them to do so after my commit described above >>>> is complete. Since the SVN repo will remain online, it should be possible >>>> for any committer to do this last step at any time after my commit is >>>> complete. >>>> >>>> -Steve B. >>>> >>> >>> >> >
