On Wed, Mar 16, 2011 at 2:45 AM, Arwin Arni <ar...@collab.net> wrote:
> Well, the reason is that both --parents and --set-depth make permanent > changes to the WC which will not be reported in the output at all.. If the > user is passing these parameters, he has a fair idea of what these > "invisible" changes are, and so shouldn't be adding them to a dry-run > command. (Maybe we could just make them FALSE during a dry-run update so it > doesn't throw those errors that I coded. The user will be oblivious to this, > as the output isn't going to change in any way) It looks like Julian beat me to it, but I was just going to say that it is not true that these options do not produce output. There is no explicit message about setting depth, as an example, but the effect of making that change has a definite impact on what update will do. I have no idea how we would implement this with a --dry-run option but we should probably figure it out before we add the option. If I am a user and there is a --dry-run option I might want to use it to see what the effect of using --set-depth is going to be on my working copy. -- Thanks Mark Phippard http://markphip.blogspot.com/
