Bill Sommerfeld wrote On 02/17/06 05:35,: > On Fri, 2006-02-17 at 00:43 -0800, Stephen Hahn wrote: > >>>As a user I would like to add the following features to the list of >>>requirements: >>>1. Preview. >>> Each transaction should have a preview mode, which allows to see what >>> will happen >>> during transaction, but without any changes in developer's and >>> integration areas. >> >> A preview mode, or dry run mode, or do nothing mode is not strictly >> necessary on transactions. An implementation might instead choose to >> have an accurate child status transaction. Because of this >> equivalence, neither E3 nor C11 require a preview mode. > > > yep, though preview/dry run has an important usability advantage; when > you get to the point where you're ready to putback/commit/integrate, you > can do a dry run and check the output, then (using a shell with history > editing) delete the "-n" or "--dry-run" or whatever the option is out of > the previous command and run it for real. > > - Bill
I agree with Bill. And there is one more advantage: the output of 'putback -n' can be used to specify the exact list of files for the real putback, so the transaction will be done much faster, which means "parent" workspace will be locked for shorter time. And 'bringover -n' is extremely useful, because it allows to check the synchronization *without* locking the workspaces. _______________________________________________ tools-discuss mailing list [email protected]
