Thomas Arendsen Hein wrote:
I think there is ample precedent for '-n' in UNIX commands and to me the ability to simulate actions accurately is a longstanding strength of Teamware.
Note also that cvs makes heavy use of "-n" options.
Mercurial already has -n/--dry-run for some commands. The difference with pull/incoming and push/outgoing is that the behaviour is different: 1. The incoming command when used with remote reposities really has to transfer everything, therefore it has a --bundle option to store the received data in a bundle file which then can be really pulled. 2. As noted above the outgoing command doesn't try to simulate a push. 3. incoming and outgoing do something which pull/push don't: They display changesets like 'hg log', optionally even with patches (option '-p' like 'hg log' and friends).
Maybe these are reasons why I really want -n for push/pull. Leave incoming around for the case where I want to pull over everything that would be pulled over, but without incorporating it yet. I don't fully understand the difference between push and outgoing, but what I really want is to know that if I did a push right now, what would it do and would it succeed? If outgoing doesn't tell me that, I want something else that does. I also don't think I want something with substantially different output in the "real" and "dry run" cases. _______________________________________________ tools-discuss mailing list tools-discuss@opensolaris.org
