On Wed, Nov 08, 2006 at 02:39:14PM -0800, Mike Kupfer wrote: > Some of the priorities on the migration page are guesses based on only a > vague understanding of what the tool does. I can't respond to your > point about daily_update until I see the ON tools page (or until someone > gives me a better idea of what daily_update does).
daily_update maintains the "daily" workspace, which is used by putback_diffs to spit out the diffs between the gate and the daily workspace after every putback. putback_diffs then does a bringover from the gate to the daily workspace so that the next set of diffs is correct. daily_update runs shortly after the clone to make sure that the daily workspace is in fact in sync with the gate, in case one of the putback_diffs runs earlier in the day failed to update it properly. I don't think it's once had to do anything in the lifetime of Nevada. We won't need the daily workspace for this kind of crap with mercurial, as we can just log the patch straight out of the changegroup hook. Or not bother logging it at all, since we can retrieve it at any time. :) Danek _______________________________________________ tools-discuss mailing list [email protected]
